2 ms·
> ... be otherwise explained? A few things: you asked about it being unavoidable. Remember, the rust compiler and standard library is a near decade long projec
by steveklabnik 10y ago
> ... be otherwise explained?
A few things: you asked about it being unavoidable. Remember, the rust compiler and standard library is a near decade long project evolving extremely rapidly. This means that many things in the compiler aren't exactly done the best possible way as if you wrote things from scratch today. The standard library is shaping up. But a _lot_ of time and effort has been put in towards modernizing things. Years of your language changing as you implement your language is a recipe for lots of tech debt.
Furthermore, you asked about a lot of stuff that's _not_ in the standard library too, so it's not clear that pointing at the standard library is a good way to demonstrate how those things are developed as well. And while we have developed a decent set of stuff in the standard library for these cases, it's not like stuff just gets added anymore, either.
So, lots of reasons.
- acqq 10y agoStrange: the changes in the C++ compiler were typically done to allow better standard libraries, and here is implied that it's hard for the libraries to use the language improvements as the Rust compiler gets better, and that they would otherwise use significantly less "unsafe" parts... I'd have to see some examples to be convinced.
- steveklabnik 10y agoI'm not implying that it's hard in a clean-room sense, I'm implying that changing things over time means you might end up with different code than if you did it clean-room today. The interfaces matter a lot more than the implementations; we spent a lot of focus on the actual interfaces, stabilized them, and internal improvements are always landing.