4 ms·
Honestly, I found dealing with generics worse than the borrow checker. Since the compiler wants everything to be sized, code that I think should work (i.e. usin
by allengeorge 10y ago
Honestly, I found dealing with generics worse than the borrow checker. Since the compiler wants everything to be sized, code that I think should work (i.e. using generics and traits) will sometimes just not compile. In fact - I'm dead in the water facing an issue like that right now. That is, by far, the most frustrating thing in using Rust.
- steveklabnik 10y agoHave you asked for help on one of the various forums? If something is leaving you dead in the water, I'd like to help you fix that.
- EugeneOZ 10y agoJust ask for help in IRC or your local Rust community and you'll get help. If you want - post here link to gist.github and I'll try to help.
- burntsushi 10y agoCan you describe the issue? Perhaps someone can help. I don't know if it helps you or not, but you can specify that a type parameter need not be sized with the ?Sized bound. e.g., The `Path::new` constructor is defined as `fn new<S: AsRef<OsStr> + ?Sized>(s: &S) -> &Path`. This means `S` can, for example, be `str`, which is an unsized type.
- allengeorge 10y agoThanks guys - much appreciated. I'm on my mobile in another country, so, can't post a link right now - but I will later tonight when I've WiFi. BTW - this reaction is why I continue to work with Rust; the community is awesome! (Dealing with trait objects and generics...less so)