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
Originally posted by NicholasSterling October 30, 2022
Interesting crate -- thanks for the contribution.
This is a minor point, but when I saw AnyString I thought "oh no, if I had an &str, I wouldn't necessarily want it to be converted to a String." But the target type for AnyString is actually &str. So this leaves me with two thoughts:
Would it be clearer to call that AnyStr?
Do you want an AnyString (with a target type of String) too?
The text was updated successfully, but these errors were encountered:
I'm leaning now to changing the current AnyString (which produces a &str) to AnyStr. I'll increment the version of the library because this would be a breaking change.
Then the question would be is should there be an "AnyString" that creates a String. I'm leaning towards not doing that until/unless there is demand.
Discussed in #2
Originally posted by NicholasSterling October 30, 2022
Interesting crate -- thanks for the contribution.
This is a minor point, but when I saw AnyString I thought "oh no, if I had an &str, I wouldn't necessarily want it to be converted to a String." But the target type for AnyString is actually &str. So this leaves me with two thoughts:
The text was updated successfully, but these errors were encountered: