Remove gopher from list of special schemes

[CYBAI]

whatwg/url#453
web-platform-tests/wpt#19770

[jamestomasino]

whatwg is heavily focused on HTML. Their choice to drop support for other protocols is understandable based on those goals. Rust is bigger than just the web, as are URLs, despite their opinion.

There are gopher clients in the wild relying on this implementation in rust-url. Gopher still exists and has users. Dropping support here will not significantly change the library, but it will have significant impact on those users.

[SimonSapin]

Making a scheme "non-special" doesn’t mean you can’t use it, only that some details of the parsing algorithm are different.

[jamestomasino]

Egg on my face! What would actually change from this, then? Will gopher urls still know that gopher runs on Port 70 by default?

[tmccombs]

Making a scheme "non-special" doesn’t mean you can’t use it, only that some details of the parsing algorithm are different.

Which also changes the behaviour of certain setter methods, since they follow the parsing algorithm. See #577 and #579

[djc]

This was fixed in 2f204d0.

[tmccombs]

I wonder if it would make since to have some way for users of rust-url to specify that a scheme is "special". Perhaps a method on ParseOptions either to force "specialness", or give a list of additional schemes to treat as "special"?

[djc]

Seems like a decent proposal on the face of it. Let's discuss in #577?