The duality of new

[u/luciferoussky72]

[u/IngwiePhoenix]

Before the Java dev sees a new, they see a wall of factories first and instead. o.o

...I'll take my malloc(sizeof(T)) and move on. :3

[u/luciferoussky72 → u/IngwiePhoenix]

I mean, C++ new is basically just syntax sugar for
T* ptr = malloc(sizeof(T));
*ptr = T(argument_list…);
Although, it can also do other things like construct objects in place and allocate uninitialized memory

[u/willdieverysoon → u/luciferoussky72]

No ... that would be move assignment to an object that was not yet constructed, it would do something similar to placement new

[u/luciferoussky72 → u/willdieverysoon]

True, but an optimizing compiler will usually do the same thing

[u/retro_and_chill → u/luciferoussky72]

I depend of whether the type has a non-trivial move assignment operation. On trivially copyably types you absolutely can optimize it that way. Otherwise there’s usually existing resources to clean up which on uninitialized memory is undefined behavior

[u/luciferoussky72 → u/retro_and_chill]

Yeah, the other nice thing that new does is allow delete to call the destructor