4 ms·
> Rust is a systems language pursuing the trifecta: safe, concurrent, and fast. > It was also discovered that we closed the second largest number of issues of
by tomp 13y ago
> Rust is a systems language pursuing the trifecta: safe, concurrent, and fast.
> It was also discovered that we closed the second largest number of issues of any repository on GitHub!
Doesn't make me very confident...
- octo_t 13y agoPursuing != is. Its a language in the stages of infancy and under active development, of course there are bugs. Its not even at version 1.0 yet!
- dbaupp 13y agoA lot of the issues included in that count are pull requests (including ones adding awesome new features, not just fixing bugs), and we get a reasonable number of duplicate filings (which doesn't particularly matter: it gives us more test code for the suite).
- banachtarski 13y agoSo would you be more confident in repositories that closed 0 issues? I can point you to plenty of those.
- coldtea 13y ago>Doesn't make me very confident... This makes no sense at all. For one, it's a language under heavy development. Obviously most of these issues where things not implemented already, library ftuff missing, temporary implementations that had to be changed to the new one, small and bigger regressions due to syntax and library changes etc etc. Second, you'd rather those issues remained open? Or that magically some rainbow unicorns perhaps would have prevented the language from having any issues in the first place? What matters is that the number of issues drops low enough, as the language tries to reach version 1.0. And what the announce here is very well aligned with that goal.
- Pacabel 13y agoThere's no need to be snide. I think he may just be surprised that those bugs still occurred, given how the Rust toolchain is itself implemented in Rust, by the designers of Rust, and how Rust is supposedly designed in a way that prevents bugs to a larger extent than other languages do. It's understandable where he's coming from. If those who know Rust the best are still subject to bugs in their Rust code, it's perfectly valid and reasonable to wonder if the rest of us really be any better off than we are with Java, or C#, or Python, or whatever language(s) we're currently using.
- coldtea 13y ago>I think he may just be surprised that those bugs still occurred, given how the Rust toolchain is itself implemented in Rust, by the designers of Rust, and how Rust is supposedly designed in a way that prevents bugs to a larger extent than other languages do. Well, then what he probably doesn't understand is that those bugs are not in their majority memory bugs or sound-ness bugs or bugs in the things Rust is supposed to protect you from. Most are issues related to half or mis-implemented features, syntax that changed and libs that need to change in accordance, etc. If I have: random() { return 6;} as a stub, I could post an issue to remind me to implement a actual random number generator later. Doesn't mean the language has some inherent problem itself.
- DasIch 13y agoIssues are not bugs just because bugs happen to be issues. Depending on development workflow every contribution might be made as a pull request and therefore show up as an issue. Also most projects tend to underreport issues, in that a lot of bugs are fixed or features implemented without creating an issue. You can easily achieve a high number of issues compared to other projects, just due to workflow and by using issues heavily to document what you are doing. What would be concerning is a large number of old open issues or if the number of opened issue is significantly larger than the number of issues being closed.