3 ms·

Or, one day, Rust :P. Or does Rust's optional GC get in the way? I'm not really familiar with that part of the language.

• steveklabnik 13y ago
  Rust is written in Rust. (The compiler currently makes heavy use of `unsafe`, in my understanding. At least for now.)
  • yoklov 13y ago
    Not an expert, but my understanding was that most of those were either from bindings to unsafe functions (e.g. C++ functions from LLVM) or false positives from the compiler dealing with the 'unsafe' keyword in the code its compiling.
• kibwen 13y ago
  It's increasingly possible to write Rust code without needing the runtime at all; this is what's enabling the current effort to rewrite the runtime from C++ to Rust itself. However, there are some restrictions imposed if you choose to shed the runtime: no use of garbage-collected pointers, and concurrency will be either unavailable or somewhat restricted (i.e. mapping tasks to OS threads rather than green threads). https://github.com/mozilla/rust/issues/3608 https://github.com/mozilla/rust/issues/3608 Writing the Go runtime in Go would require the similar ability to do without all the services that are currently provided by the runtime. That is, unless you want your runtime to recursively require itself to infinite depth. :) I'm sure it's theoretically possible, but considering that two of the language's largest selling points are concurrency and memory safety via GC, a theoretical runtime-less dialect of Go would be so near to C that it might not really be worth the effort.