Re: Boost.URL Proposal

From: Boris Kolpackov (boris_at_[hidden])
Date: 2022-02-18 09:23:06

Alan de Freitas via Boost <boost_at_[hidden]> writes:

> Vinnie Falco and I are looking for a review manager for the library
> that we hope will become Boost.URL.
>
> [...]
> 
> - The library implements the specification as in RFC3986
> <https://datatracker.ietf.org/doc/html/rfc3986> + its errata
> <https://www.rfc-editor.org/errata/rfc3986>
>     - Non-ASCII characters are not considered valid URLs
>     - Other specifications such as RFC3492
> <https://datatracker.ietf.org/doc/html/rfc3492>, WhatWG
> <https://url.spec.whatwg.org/>, or any other form of relaxed parsing are
> out of the scope of the library

We needed something similar but with support for various relaxed
parsing cases. The approach we ended up with is to customize the
types and parsing of various URL components with template parameters
and traits:

https://github.com/build2/libbutl/blob/master/libbutl/url.hxx

I am not saying this approach is better than the proposed library.
Just thought I'd mention an alternative design to meditate upon
(I wonder if it would be possible to implement url_view as just
an alias for url<string_view, ...>).