4 ms·
It's a very detailed but also complicated proposal. It seems like it aims at some kind of inheritance as well? I would prefer it it were simpler.
by kzrdude 11y ago
It's a very detailed but also complicated proposal. It seems like it aims at some kind of inheritance as well? I would prefer it it were simpler.
- steveklabnik 11y agoIt's going to end up being a key part of the future inheritance proposal, but that's not a part of this RFC at all. > I would prefer if it were simpler. If you have thoughts about how to simplify it, please get involved in that thread! We don't actively try to introduce complexity, but sometimes, features are just inherently complex. There's also the case that sometimes features are easier to use than they are to define. I think this will be one of those kinds of features. At its core it just means that if you have a Vec<i32> and you also have impl<T> Foo for Vec<T> you'll be able to define an additional impl Foo for Vec<i32> and your Vec<i32> will use that one instead of the more general Vec<T> one.
- gbersac 11y agoNow I get it. It is not that complicated after all.