Recent searches
Search options
Administered by:
Looks like the "break rust" easter egg that I added last year is being removed from GCC #Rust over being "bloat" and "insulting the GCC users"
Oh well
gcc.gnu.org114629 – rust-ast-resolve-expr contains bloated code for funny_error
@bugaevc Could you please add the RustLang tag? 
Background: https://fosstodon.org/@mo8it/112056453394255413
FosstodonMo :ferris: :tux: (@mo8it@fosstodon.org)I am starting a Mastodon campaign :omya_mastodon:
Every time I see a post with only the #Rust tag, I will kindly ask the poster to use #RustLang instead 😇
My feed is full with unrelated content about the film, the game and of course photography of rusty metal 🤬
I will also only post using the #RustLang tag starting from now 😤
You can join me! 🤗
The goal is to let the usage of the #Rust tag vanish so people can only follow #RustLang 😃
@bugaevc if you can, let the maintainers know that the ICE behavior special casing isn't *necessary*, as failing the compilation due to unknown identifier will already match the relevant behavior of the language. The conversation in that thread still feels a bit weird.
@ekuber it certainly isn't necessary for correctness, IDK why people brought that up, it is strictly a joke. I left an explanation in the source code, perhaps they've missed it