fluent-uri-rs
fluent-uri-rs copied to clipboard
yescallop
A full-featured URI handling library compliant with RFC 3986.
Hiya! From a quick cursory glance over the API of this crate it looks like it would be possible to support `no_std` without too much trouble, mostly just cfging all...
resolve
Is it possible to resolve one URI in the context of another? Given base: ~~~ https://volvoforums.com ~~~ and reference: ~~~ forum/ ~~~ return: ~~~ https://volvoforums.com/forum/ ~~~ Examples: - https://www.rfc-editor.org/rfc/rfc3986#section-5.4 -...
Comparison is part of the spec: https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.
Implementation notes: * Error kind is important for distinguish outside library, which exact error has been occurred. Checking a formatted message is not an option as it's non-stable as it...
Hi, I'd like to ask for a an improvement to `fluent_uri::Uri` implemenation (as of version `0.2.0-alpha.3` published on [crates.io](https://crates.io/crates/fluent-uri)). There's two methods `is_absolute_uri` and `is_relative_uri`. How can I build a...
ResolveErrorKind is important to decide what error has been occurred before displaying it. Developer should decide how to present it as their might include context, translate as their please and...
There is too much unsafe code in version `0.1`. It is nearly unmanageable. Yet it is not possible to forbid unsafe code because of `Uri` and `Uri::borrow`. At least we...
for reference: https://github.com/yescallop/fluent-uri-rs/issues/17
It would be nice to support IRI handing as many standards (see [References to RFC 3987](https://datatracker.ietf.org/doc/rfc3987/referencedby/) and [RDF 1.1](https://www.w3.org/TR/rdf11-concepts/)) depend on IRIs. The current plan is: - Add `Iri` and...