cqwrteur
cqwrteur
The constructors in the library need some cleanups. It is a completely mistake for too many duplications.
The vector constructors need completely rewrite. It wasn't me who wrote the code, sorry.
What about now? Is it fixed in next branch?
Has it fixed? I have added into the test.
I do not know whether no one is proposing an is_zero_default_initialization which allows the vector to skip initialization for types like int
Do you have any interests on helping me maintain the code? I think you have much more knowledge on how to correctly write containers than me.
You can join our discord if you have more suggestions. I am still confused on what uninitialized_relocate is supposed to do
> > I am still confused on what uninitialized_relocate is supposed to do > > @trcrsired: Ah. See [[uninitialized.relocate]/1](https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p1144r10.html#wording-uninitialized.relocate). `uninitialized_relocate` simply relocates a range of objects from source to destination....
> > Why are not these uninitialized functions constexpr? > > These functions (`uninitialized_move` etc.) were introduced in C++17. Prior to C++20, it was impossible to manually construct or destroy...
Hi. i was busily working on my paper so i was not working on this. Now is it fixed?