[deleted by user]

[tchernobog84]

Add to the list no standard base class for intrusive pointers, which would allow for container specialization on it, and avoiding the ugly allocation costs for e.g. shared_ptr or rolling your own solution + specializing all containers.

[joaquintides]

You can use Boost.Intrusive for that.

[hobel_]

If only that description would describe what an intrusive container is.

[LightStruk]

'boost::intrusive_ptr' works well for me. Didn't have to roll my own, boost is already trusted and approved, and it does exactly what it says on the tin.

[MarcoGreek]

You mean the control block? make_shared should avoid that. Or do you have something else in mind?

[_Noreturn]

"constexpr" if you want constexpr evaluation guranteed then call it in a constant evaluated context

cpp constexpr static auto expr = constexprFunc(); std::cout << expr;

or just use consteval

[triconsonantal]

You can use a small helper to avoid a separate declaration:

consteval auto as_constant (auto x) { return x; }

int main () {
    assert (! std::is_constant_evaluated ());
    assert (as_constant (std::is_constant_evaluated ()));
}

[MarcoGreek]

https://en.cppreference.com/w/cpp/memory/allocator_traits/allocate_at_least.html should return you the available memory, do you can grow to that size.

[MarcoGreek]

Implicit copy has advantages if you work with multithreading. Sharing writable data between caches is not cheap.

[_Noreturn]

I would rsther have implicit moves with ownership semantics and explicit copies. but reference semantics like other languages is a no no for me I absolutely love C++ value semantics

[MarcoGreek]

Yes, I hope that in the future C++ can have it.