You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation has type Error = InvalidUri, but this can never occur.
If we decide that #96 should be changed or removed, then this could be updated to correctly return an InvalidUri error.
If not, we might want to consider that a From<T> will likely end up in a TryFrom<T> where Error = ! blanket impl. Can we have some uninhabited type in convert.rs as the Error, and then alias it to bang or something later?
The text was updated successfully, but these errors were encountered:
The current implementation has
type Error = InvalidUri
, but this can never occur.If we decide that #96 should be changed or removed, then this could be updated to correctly return an
InvalidUri
error.If not, we might want to consider that a
From<T>
will likely end up in aTryFrom<T> where Error = !
blanket impl. Can we have some uninhabited type in convert.rs as theError
, and then alias it to bang or something later?The text was updated successfully, but these errors were encountered: