Displaying 9 results from an estimated 9 matches for "svector".
Did you mean:
vector
2020 Nov 13
6
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...e my updates
to ProgrammersManual.rst in the patch)
- how much we want to bulk migrate code vs let it organically grow.
Replacing SmallVector<T, 0> with Vec<T> should be completely mechanical.
Replacing SmallVector<T, N> for general N would be a lot more work.
- of course: naming. SVector/Vector were floated in the patch as well and
seem ok. SmallVec was rejected as it was a prefix of SmallVector (messes up
autocomplete).
Looking forward to a world with fewer guessed SmallVector sizes,
-- Sean Silva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: &l...
2020 Nov 16
2
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...ual.rst in the patch)
> > - how much we want to bulk migrate code vs let it organically grow.
> Replacing SmallVector<T, 0> with Vec<T> should be completely mechanical.
> Replacing SmallVector<T, N> for general N would be a lot more work.
> > - of course: naming. SVector/Vector were floated in the patch as well
> and seem ok. SmallVec was rejected as it was a prefix of SmallVector
> (messes up autocomplete).
> >
> > Looking forward to a world with fewer guessed SmallVector sizes,
> >
> > -- Sean Silva
> > ________________________...
2020 Nov 16
0
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...es to ProgrammersManual.rst in the patch)
> - how much we want to bulk migrate code vs let it organically grow. Replacing SmallVector<T, 0> with Vec<T> should be completely mechanical. Replacing SmallVector<T, N> for general N would be a lot more work.
> - of course: naming. SVector/Vector were floated in the patch as well and seem ok. SmallVec was rejected as it was a prefix of SmallVector (messes up autocomplete).
>
> Looking forward to a world with fewer guessed SmallVector sizes,
>
> -- Sean Silva
> _______________________________________________
> LLVM D...
2020 Nov 16
0
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...anual.rst in the patch)
>> > - how much we want to bulk migrate code vs let it organically grow. Replacing SmallVector<T, 0> with Vec<T> should be completely mechanical. Replacing SmallVector<T, N> for general N would be a lot more work.
>> > - of course: naming. SVector/Vector were floated in the patch as well and seem ok. SmallVec was rejected as it was a prefix of SmallVector (messes up autocomplete).
>> >
>> > Looking forward to a world with fewer guessed SmallVector sizes,
>> >
>> > -- Sean Silva
>> > ______________...
2020 Nov 16
2
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...ch)
> >> > - how much we want to bulk migrate code vs let it organically grow.
> Replacing SmallVector<T, 0> with Vec<T> should be completely mechanical.
> Replacing SmallVector<T, N> for general N would be a lot more work.
> >> > - of course: naming. SVector/Vector were floated in the patch as well
> and seem ok. SmallVec was rejected as it was a prefix of SmallVector
> (messes up autocomplete).
> >> >
> >> > Looking forward to a world with fewer guessed SmallVector sizes,
> >> >
> >> > -- Sean Silv...
2020 Nov 17
2
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...gt; > - how much we want to bulk migrate code vs let it organically
> grow. Replacing SmallVector<T, 0> with Vec<T> should be completely
> mechanical. Replacing SmallVector<T, N> for general N would be a lot more
> work.
> >> >> > - of course: naming. SVector/Vector were floated in the patch as
> well and seem ok. SmallVec was rejected as it was a prefix of SmallVector
> (messes up autocomplete).
> >> >> >
> >> >> > Looking forward to a world with fewer guessed SmallVector sizes,
> >> >> >
>...
2020 Nov 17
0
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...atch)
>> >> > - how much we want to bulk migrate code vs let it organically grow. Replacing SmallVector<T, 0> with Vec<T> should be completely mechanical. Replacing SmallVector<T, N> for general N would be a lot more work.
>> >> > - of course: naming. SVector/Vector were floated in the patch as well and seem ok. SmallVec was rejected as it was a prefix of SmallVector (messes up autocomplete).
>> >> >
>> >> > Looking forward to a world with fewer guessed SmallVector sizes,
>> >> >
>> >> > -- Sea...
2020 Nov 17
1
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...ulk migrate code vs let it organically
>>> grow. Replacing SmallVector<T, 0> with Vec<T> should be completely
>>> mechanical. Replacing SmallVector<T, N> for general N would be a lot more
>>> work.
>>> >> >> > - of course: naming. SVector/Vector were floated in the patch as
>>> well and seem ok. SmallVec was rejected as it was a prefix of SmallVector
>>> (messes up autocomplete).
>>> >> >> >
>>> >> >> > Looking forward to a world with fewer guessed SmallVector sizes,...
2020 Nov 17
0
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...uch we want to bulk migrate code vs let it organically
>> grow. Replacing SmallVector<T, 0> with Vec<T> should be completely
>> mechanical. Replacing SmallVector<T, N> for general N would be a lot more
>> work.
>> >> >> > - of course: naming. SVector/Vector were floated in the patch as
>> well and seem ok. SmallVec was rejected as it was a prefix of SmallVector
>> (messes up autocomplete).
>> >> >> >
>> >> >> > Looking forward to a world with fewer guessed SmallVector sizes,
>> >>...