Re:New SSA Back End for the Go Compiler (2015)
by killercup on Tuesday April 05, 2016 @10:49AM
(#11430789)
Some people have worked on a Rust REPL, but it wasn't really useable last time I checked. Part of the motivation to develop this was the possibility to use LLVM as a JIT, which is pretty nice.
Personally, I would love to see this as part of an IDE that can execute _parts_ of a Rust file with various inputs to quickly see if a function behaves as expected (this could also be easily converted into test cases.)
Re:New SSA Back End for the Go Compiler (2015)
by nickpsecurity on Tuesday April 05, 2016 @09:32PM
(#11435966)
That's the idea. They're great for exploratory programming. In LISP, safety was optional. This was actually OK... would be in Rust... if your goal in that mode was to understand requirements, algorithm, solution space, etc. Get an idea of how you might handle it. Then, turn safety back on, try to get a solution going. When it works, compile that module. Future tweaks do incremental compilation.
Rapid development cycle doing features this way.
Now, the only thing left is a real-time interpreter with live code updates. I recall the LISP box could do instant changes interpreted for exploratory stuff on running image. Solidify that super fast with per-function, typed compiles. Plus do whole program compiles if you had to. So yall getting close but what's odds of those other features happening?
Note: Live, interpreted image with save the world also makes it easier to debug stuff locslly and remotely. Send devs the whole, running state.