4 ms·

When I read it, I think two things : 1- Great job. This is both innovative and powerfull. Like the idea to test nighties on every crate available on github. I

by gbersac 11y ago

When I read it, I think two things : 1- Great job. This is both innovative and powerfull. Like the idea to test nighties on every crate available on github. I am sure no other language does it. 2- So much feature may be a little disappointing. Take specialization. It may be interesting, but I don't even understand what it is. And I am not a beginner anymore ! Don't you fear that, by adding more and more feature, rust will become like the language it is aiming to replace (c++) : a huge mess of feature ? That being said, I am definitely a rust enthusiast (I bought the book https://www.kickstarter.com/projects/1712125778/rust-programming-concepts-book https://www.kickstarter.com/projects/1712125778/rust-program...). Carry on !

steveklabnik 11y ago
> Take specialization. It may be interesting, but I don't even > understand what it is. That's fair, it's hard to put a full motivation in these kinds of posts. The RFC contains the full proposal, as well as a motivations section that hopefully makes it more clear: https://github.com/rust-lang/rfcs/pull/1210 https://github.com/rust-lang/rfcs/pull/1210 TL;DR: specialization lets you also implement a more specific version of something that's generic. This lets you take advantage of this extra detail for various ends, like making a particular implementation more efficient than a general one could be.
- 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 ago
    It'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 ago
      Now I get it. It is not that complicated after all.

by gbersac 11y ago

steveklabnik 11y ago

> Take specialization. It may be interesting, but I don't even > understand what it is. That's fair, it's hard to put a full motivation in these kinds of posts. The RFC contains the full proposal, as well as a motivations section that hopefully makes it more clear: https://github.com/rust-lang/rfcs/pull/1210 https://github.com/rust-lang/rfcs/pull/1210 TL;DR: specialization lets you also implement a more specific version of something that's generic. This lets you take advantage of this extra detail for various ends, like making a particular implementation more efficient than a general one could be.

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 ago
  It'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 ago
    Now I get it. It is not that complicated after all.