consider lowering fundamental types to separate modules

[tayloraswift]

this library contains a lot of useful features (e.g. IPv4Address, percent encoding, etc.) that could be lowered into separate modules that the downstream WebURL module imports. this means some parsing APIs might need to become cross-module extensions, but this shouldn’t be a problem for modern documentation tooling.

from a brief inspection of the codebase, it appears the main blocker is a number of dialectical utility APIs in Sources/WebURL/Util. so the first step might be to lower the utility support to separate module. (sadly, this means a lot of @inlinable internal/@usableFromInline internal things must become public and pollute standard library namespaces, but that is just a fact of swift…)