News for hackers. Stuff that matters.
Re:Achievement unlocked: rustc segfault by woodruffw on Sunday April 10, 2022 @05:25PM (#30981874)
Not to besmirch Pony (I think it's a very interesting language), but isn't some of this a base sampling error? There are probably a few orders of magnitude more engineers writing Rust (and therefore running `rustc`), so we'd expect crashes in Rust to surface more frequently.
Re:Achievement unlocked: rustc segfault by rurban on Sunday April 10, 2022 @05:30PM (#30981910)
Not in memory safe languages, sorry.
Re:Achievement unlocked: rustc segfault by woodruffw on Sunday April 10, 2022 @05:33PM (#30981937)
I'm not sure I understand. Rust is memory safe, and the memory unsafety happening here isn't in Rust itself: an IR generation bug in Rust is causing memory unsafety in LLVM, which is written in C++.

(Besides: If GitHub's stats are correct, `ponyc` seems to be >60% C and C++?)

Re:Achievement unlocked: rustc segfault by saghm on Sunday April 10, 2022 @08:27PM (#30983206)
Compilers for memory-safe languages can't have bugs in them?
Re:Achievement unlocked: rustc segfault by 3836293648 on Monday April 11, 2022 @07:59AM (#30987489)
Compilers for memory safe languages written in the same memory safe languages should be expected to have to same guarantees as any other program written in that language
Re:Achievement unlocked: rustc segfault by UncleEntity on Monday April 11, 2022 @10:32AM (#30989286)
I think that’s the fifth Futamura projection — compiling a compiler with itself cancels out bugs.