4 ms·
They promised improvements in keeping backwards compatibility, i.e. building old code on new rust. No one promised forward compatibility, building new code on o
by Macha 6y ago
They promised improvements in keeping backwards compatibility, i.e. building old code on new rust. No one promised forward compatibility, building new code on old rust.
- flohofwoe 6y agoYeah ok, makes sense of course. It's still a somewhat strange decision on the project's part. It's basically similar to using C++20 features only six months after the first C++ compilers support C++20. If that's a one-time thing during development of the framework it's probably fine. But if in 5 years the project still reqiures a less than 6-months old compiler version, I'd be worried ;)
- nicoburns 6y agoWhy? The advantage of having a single Rust compiler is that there is almost never any reason to use an old one. There are some cases where I can see that using a pinned compiler version would be important: if you are doing mission-critical embedded or financial programming and need a verified compiler. But none of those apply to game development.
- flohofwoe 6y agoI see having a single compiler instead of multiple competing compilers more as a bug than a feature, at least in the long run. It's fine as long as the language is in "exploration phase", but hopefully we'll see more independent Rust compilers in the future (e.g. https://github.com/Rust-GCC/gccrs https://github.com/Rust-GCC/gccrs)
- nindalf 6y agoWhether it’s a bug or a feature is immaterial to the present discussion of what you should do when there’s one implementation. The reasonable thing to do is to upgrade the compiler when a new one comes out. Each upgrade is generally pain free because the team goes to great lengths to ensure backwards compatibility. They compile every single open source code base with the latest release before putting it out. In that context, I don’t see the issue with Rust codebases depending on the latest compiler. I understand that it’s done differently with C/C++ and that’s fine. I don’t see why both models can’t work.
- umanwizard 6y agoOne significant reason to use an old compiler is if you want to avoid having multiple package managers on your system (i.e. rustup _and_ apt). The normal philosophy on typical Linux systems is in fact _not_ to require bleeding-edge compiler versions; there’s no “gccup” program. It’s the rust project that is proposing a new and different model.
- linkdd 6y agoI would add that having multiple package managers on the same system can be a hazard. For example, NEVER install a Python package globally with pip on a Debian System, it WILL conflict with Debian packages (and you'll be very unhappy and confused on the next apt remove or pip uninstall).
- remexre 6y agoRust/Cargo definitely learned what not to do from pip...
- nicoburns 6y agoIMO you shouldn't really ever be using system provided versions of compilers or programming languages. Linux distros are significantly constrained in terms of which language versions they package because they need to use those versions to package packages which rely on those languages. That, along with the fact that most distros only release every 6 months to 2 years means that you generally have quite out of date versions. It seems that rustup itself is not currently packaged by debian or other linux distros which seems to be a bigger issue. If you could `apt install rustup && rustup install stable` then that seems preferably in pretty much every way to `apt install rust` and getting an old version.
- aww_dang 6y agoSrc based distros tend to be a little better with this.
- rapsey 6y agoYou don't need to have it installed in /usr. It can be (and is by default) completely contained within your home folder. Anyone not doing it this way is just making life needlessly hard for himself and his problems should be ignored entirely.
- pjmlp 6y agoExcept when using compiler based distributions, then again this is about game development and 1% userbase is irrelevant.