[Feature] Allow customization of special schemes

[lufte]

• Note that this crate implements the URL Standard not RFC 1738 or RFC 3986

I would like to work with some non-special schemes (gemini, gopher...) but get the same behaviour as if they were special, like IPv4 hosts and no empty hosts. I understand it's not standard, but it would be useful in many cases. A compile-time setting wouldn't even require any change to the API.

Would this be considered? I am willing to create a PR if needed.

[annevk]

I think a better solution would to write a wrapper URLProcessor crate of sorts that does this. We shouldn't tweak how URLs are parsed.

[tmccombs]

How would that work? The current API doesn't really provide a good way to create such a wrapper.

[annevk]

Sorry, I didn't mean a literal wrapper. Just a conceptual function that takes a URL and returns a "ProcessedURL".