3 ms·
With Rust you can also convert to `Vec<T>` where T is either `u8` or `u16` and use generics to work on any. ️ And there are probably handful of libraries that
by dpc_pw 7y ago
With Rust you can also convert to `Vec<T>` where T is either `u8` or `u16` and use generics to work on any. ️
And there are probably handful of libraries that would help with all that too. Also - whatever convenient functionality you might want, can be added in the future without issues. Hardly a language flaw - just a minor unimplemented functionality.
- klodolph 7y ago> With Rust you can also convert to `Vec<T>` where T is either `u8` or `u16` and use generics to work on any. That’s a very cumbersome way of doing things. I would love to see an illustration. It also involves a ton of conversions: if want to parse a command-line flag which contains a file path, it would go: wchar_t -> OsString -> Vec<u16> -> OsString -> wchar_t. It also makes it difficult to use Rust APIs in a more or less idiomatic way. > Hardly a language flaw - just a minor unimplemented functionality. It’s a flaw in the standard library, not the language. When you say that it’s minor, all you’re doing is saying, “I don’t care about the things you care about.” That’s not really an argument, just a statement of your own personal opinion.