Conversation

I am pretty "eh" about gcc-rs but my position is that if it lacks a borrow checker, it's not actually a Rust implementation, it's a codegen backend for an extremely exotic dialect of C and/or ML. Rejecting incorrect yet well-formed programs is a primary feature of Rust.
13
244
I assume there's an intent to eventually do that, but the key aspect of the language is that it admits static analysis of lifetime correctness ("borrow checking") not that you have to spend time doing static analysis every time you compile.
1
4
In order to properly use rustc to perform the type/borrow checking, you would need it to support the platform in the frontend even if it lacks a backend for it. If there was a rustc GCC backend, you could use it to bootstrap on a platform supported by GCC without a GCC frontend.
2
2
I still see people complaining that there are some legacy or weird embedded platforms supported by GCC and not LLVM. I'm not sure what those are specifically. From my perspective any serious architecture worth supporting will have a community to port GCC, LLVM and a lot more.
2
1
It has at least experimental support for them and it would be a dramatically smaller project to bring those up to the quality required by the people wanting to use Rust on those platforms. There's a lot more than Rust using LLVM and those things are increasing in usage too.
1
1
I think an alternate frontend would be a LOT more interesting if it wasn't part of GCC. Making it part of GCC makes it a lot less interesting. It makes it a pain to contribute, ties releases to GCC and Rust has a strong permissive licensing culture so that drives people away too.
1
2
Show replies