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
There are times when it is desirable to work with a struct that gives constant-time access to chars (such as Vec<char> or VecDeque<char>), but currently the APIs return a String (or take a &str as input).
Currently, users must translate to/from String to work with certain APIs (such as katakana_to_hiragana()). We should try to support iterators over char as input/output.
The text was updated successfully, but these errors were encountered:
For the input this should be easy, but for the output it's a little bit more effort. But I'm not sure this would reflect best practices, since this is true for every api which accepts &str or String
There are times when it is desirable to work with a struct that gives constant-time access to chars (such as
Vec<char>
orVecDeque<char>
), but currently the APIs return aString
(or take a&str
as input).Currently, users must translate to/from
String
to work with certain APIs (such askatakana_to_hiragana()
). We should try to support iterators overchar
as input/output.The text was updated successfully, but these errors were encountered: