Re: [filesystem] becoming worse than the standard?

From: Rainer Deyke (rdeyke_at_[hidden])
Date: 2022-08-15 11:32:52

On 15.08.22 01:34, Vinnie Falco via Boost wrote:
> I see this in the commit log for boost.filesystem:
> 
>      Deprecated path construction/assignment/appending from container types.
>      Users are advised to use string types and iterators instead of containers
>      to construct/assign/append to paths.
>      In v4, the support for containers is removed.
> 
> This can't be right now, can it? Because std::filesystem supports path
> construction from anything meeting the requirements of Source which is
> kind of range-like. Boost.URL and its downstream libraries HTTP-Proto,
> HTTP-IO, Websocket-Proto, and Websocket-IO are depending on the
> container-based interface to achieve reasonably decent syntax and
> semantics despite the limitations of the path API (which are the fault
> of the standard and not Boost).
> 
> If std::filesystem::path supports container-based parameters to
> assign() and append() then why is boost::filesystem::path removing it?

I've already given up on Boost.Filesystem due to 
https://github.com/boostorg/filesystem/issues/181.  std::filesystem 
seems to work better across different compilers/platforms, and it's 
standard.

-- 
Rainer Deyke (rainerd_at_[hidden])