Removal of smallvec from dependancies. #1974
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello, taking interrest with issue: #365
Disclamer: the approach is naive I know it involve a most to malloc and leaved the code untouched even allocating in a loop, mostly to began exploring the subject! :)
In crate/resolver I chosed to use a plain vec since the type:
SmallVec::<[Nameservers<P>; 2]
reached 544 bytes not sure it's small anymore. (did a littlestd::mem::size_of::<SmallVec<[NameServer<P>;2]>>()
to get the size in bytes)Why I didn't used TinyVec directly? Because it would have needed a
Default
implementation on each types ofNameservers
.If it's not the best course of action I am ok to get some mentoring! :)
Some idea I have in mind:
smallVec
is mandatory here.Default
is mandator due toTinyVec
Array
trait.