Hmm, so, I have two concerns after taking some initial work making allocation-fallible APIs for
spliceAPI gets rather complicated because it finalizes splicing operations once the return value of
Dropisn't changing any time soon, so there needs to be something separate for finalization. Perhaps the best solution is to panic when a finalization wasn't attempted before
Drop? @Simon Sapin, I want to hear what you think about this too.
Two good points, I'll take a look :)
Regarding your first Dot, do you have problems implementing
Splice itself? Do you have a code sample pushed anywhere?
Oops, only seeing this now. Using a space a good way to spell my full name but not to @mention my username :)
A few thoughts:
try_reserve. Just because an infallible API exists doesn’t mean a corresponding fallible API should be added, especially if it’s a convenience thing that can be achieved with a sequence of calls to other APIs
Dropcould be just one case of this