On Fri, 18 Mar 2022 at 10:16, Jonathan Wakely wrote:
>
> On Thu, 17 Mar 2022 at 20:44, Thomas Rodgers wrote:
> >
> > Looks ok to me. I just am curious, does the change to src/c++17/fs_path.cc
> > need to be part of this change (It's not obvious to me that it is related
> > to the other changes in
On Thu, 17 Mar 2022 at 20:44, Thomas Rodgers wrote:
>
> Looks ok to me. I just am curious, does the change to src/c++17/fs_path.cc
> need to be part of this change (It's not obvious to me that it is related to
> the other changes in the patch).
It's related. fs_path.cc uses std::array but was no
Looks ok to me. I just am curious, does the change to src/c++17/fs_path.cc
need to be part of this change (It's not obvious to me that it is related
to the other changes in the patch).
On Thu, Mar 17, 2022 at 12:01 PM Jonathan Wakely wrote:
> Tested x86_64-linux. Tom, any objection?
>
> -- >8 --
Tested x86_64-linux. Tom, any objection?
-- >8 --
This avoids including the whole of in , as the
header only actually needs std::pair.
This also avoids including in , which only
needs , std::bad_alloc, and std::terminate (which can be
repalced with std::__terminate). This matters less, becaus
