wish gcc 10 was built into ubuntu 20.04
GCC 10.1 Released
21–30 of 145 posts
Re: GCC 10.1 Released
#22Re: GCC 10.1 Released
#23wish gcc 10 was built into ubuntu 20.04
If you want the newest version of software, Ubuntu does not cater to that.
Re: GCC 10.1 Released
#24Earlier quoted context omitted.
> Rust borrow checker requires special annotations and restrictions put on the code to do its job. This is a good thing, because it makes lifetimes and ownership explicit and visible in the code. It serves the similar purpose as type annotations in function signatures. > Or having multiple mutable pointers/reference to the same object Sure you can have that with `unsafe`. And this is a good thing, because multiple mu…
> Sure you can have that with `unsafe` The parent was talking about the borrow checker so I only was talking about safe Rust code. Obviously if you consider that the entire C/C++ codebase is in a big unsafe {} block it'll work... because it won't do anything at all.
It's important to understand that unsafe doesn't turn off the borrow checker or disable any other of Rust's safety checks: if you use a reference in unsafe code, it will still be checked. The unsafe keyword only gives you access to these four features that are then not checked by the compiler for memory safety.
Re: GCC 10.1 Released
#25Earlier quoted context omitted.
You want a bleeding edge release in your non-bleeding edge LTS distribution?
it does not make sense to pair development toolchain versions with operating system versions.
One of the core ideas of working with LTS is that you can build your software on an LTS release and ship it to somebody else on the same LTS release, either as a source or as a binary.
If you want the latest GCC, that's fine, you're not forced to use the default compiler distributed with your OS. But it doesn't make sense to update the default compiler used in an LTS release. If you want that, then you don't want LTS.
Re: GCC 10.1 Released
#26Earlier quoted context omitted.
> Rust borrow checker requires special annotations and restrictions put on the code to do its job. This is a good thing, because it makes lifetimes and ownership explicit and visible in the code. It serves the similar purpose as type annotations in function signatures. > Or having multiple mutable pointers/reference to the same object Sure you can have that with `unsafe`. And this is a good thing, because multiple mu…
He wasn't criticizing Rust, he was just stating facts.
Re: GCC 10.1 Released
#27Earlier quoted context omitted.
it does not make sense to pair development toolchain versions with operating system versions.
What do you think LTS entails, exactly? One of the core ideas of working with LTS is that you can build your software on an LTS release and ship it to somebody else on the same LTS release, either as a source or as a binary. If you want the latest GCC, that's fine, you're not forced to use the default compiler distributed with your OS. But it doesn't make sense to update the default compiler used in an LTS release. I…
Yes, and updating compilers don't prevent that at all. You can use GCC 10 to ship code that will build and run on Ubuntu 12.04 without issues. Xcode 11 can ship code that works back to macOS 10.6 and Visual Studio 2019 can still optionally target windows fucking XP !
Re: GCC 10.1 Released
#28Re: GCC 10.1 Released
#29wish gcc 10 was built into ubuntu 20.04
Re: GCC 10.1 Released
#30It doesn't seem to be available on the main site or any of the mirrors I tried.
Surely it's available from here at the very least?
> or any of the mirrors I tried
Seems to be to me?
ftp://ftp.mirrorservice.org/sites/sourceware.org/pub/gcc/releases/gcc-10.1.0/