This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [v3] Add constexpr specifiers to std::shared_ptr, std::unique_ptr, etc
> I've also changed the constexpr constructors to value-initialize the
> tuple member, because only tuple's default constructor is constexpr.
Thanks. I was concerned when the first change was incorrect by
inspection, and tests were removed.... this looks to be actually
functional now.
That said, I don't really see a use for a default-constructed and
constexpr unique_ptr.... thoughts? I'm curious, and pre-coffee.
-benjamin
- References:
- [v3] Add constexpr specifiers to std::shared_ptr, std::unique_ptr, etc
- Re: [v3] Add constexpr specifiers to std::shared_ptr, std::unique_ptr, etc
- Re: [v3] Add constexpr specifiers to std::shared_ptr, std::unique_ptr, etc
- Re: [v3] Add constexpr specifiers to std::shared_ptr, std::unique_ptr, etc
- Re: [v3] Add constexpr specifiers to std::shared_ptr, std::unique_ptr, etc
- Re: [v3] Add constexpr specifiers to std::shared_ptr, std::unique_ptr, etc