Closed h7kanna closed 8 months ago
It would be better to take after StaticVec
where the type is re-exported no matter what, only with pub
if internals
is on.
Otherwise your code would fail if internals
is off. Do a cargo check
to confirm.
This way, we can standardize on crate::ThinVec
through-out the code. There are quite a few thin_vec::ThinVec
in there that you should scan through, and a few more places of use thin_vec::ThinVec
.
It is probably easier that I do it, if you prefer.
It is probably easier that I do it, if you prefer.
Sure.
It is probably easier that I do it, if you prefer.
Sure.
Alright, I'll close this.
Added alias to avoid importing thinvec separately as
Expr::InterpolatedString
accepts ThinVec now.