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 trait `AsRef<OsStr>` is not implemented for `u32`
I can see the point of AsRef<OsStr> since regular strings and paths behave as expected (Display would present a problem), but many external programs take numerical parameters.
I wonder what the consequences are of using Debug instead?
The text was updated successfully, but these errors were encountered:
Hm yeah, I wouldn’t be opposed if {x} worked if x were of an unsigned integral type.
I don’t think though that such an API is possible without dtolney trick for specialization, and I’d consider that trick to be to complex for current use case.
We might also introduce special syntax here (like we did for splats), but that won’t be discoverable.
A third alternative is to roll our own AsRef trait with a bunch of manual implementations for all types, but then it won’t be compatible with 3rd party impls of AsRef.
I can see the point of
AsRef<OsStr>
since regular strings and paths behave as expected (Display
would present a problem), but many external programs take numerical parameters.I wonder what the consequences are of using
Debug
instead?The text was updated successfully, but these errors were encountered: