Karl

Hey, I’ve been working on a new URL type for a little while now. Results are good - I believe we’re fully compliant with the standard (save for IDNA, which...

I agree that this part of the JS URL API is awkward. To give another data point: in my library WebURL, which implements the WHATWG standard in Swift, I made...

Ah my bad - the path example is okay because `decodeURI` won't unescape some reserved characters, like "/", so it will keep the path component as "AC%2FDC". But for the...

FYI I have implemented this in my Swift library: [documentation](https://karwa.github.io/swift-url/main/documentation/weburl/weburl/host-swift.enum). For low-level networking applications, you'll find that they often pass the hostname through `inet_pton` to decide whether they have an...

Since paths are opaque in those URLs, I think it is logical that we cannot resolve a relative path against them (they don't have a hierarchical structure that the standard...

> The path and query together determine what you get back from the server. It's only the fragment that's special and does something locally. Is that really something we can...

> No one ever escapes [ and ] in host, but: > - Only Go, Chrome, Python urlparse accept it > - Python urllib3, libcurl, and current spec reject it...

Related to #156 and #61 As for performance: we could use a bit-mask rather than an array of strings (since the standard only has a handful of unique validation errors)....

I've implemented the closure approach on a branch (https://github.com/karwa/whatwg-url/commits/validation-error-callback) and hooked it up roughly to the live viewer. The constructor for the `URL` type is generated from IDL or something...

So, one thing that is interesting is the module interface printing - the logic in the PR is a bit too simplistic; if the goal is to print an interface...