On Fri, Jan 22, 2021 at 10:18 AM Alan Bateman
wrote:
Yes, URL is really old and much of its legacy behavior cannot be changed
> for compatibility reasons. At some point I think all of its constructors
> need to be deprecated. So if you are making changes to URL then assume
> it will require a lot
Hello,
While looking into reducing string allocation in URL constructors, I found
the following somewhat puzzling:
// Throws MUE as expected: "no protocol: 1nvalid://resource"
// Reason: "1nvalid" is not a valid scheme (cannot start with a digit)
// See https://www.ietf.org/rfc/rfc2396.html#secti
