If there was a decent way to handle dynamic evaluation though, it could certainly be added, and without too much issue I would imagine :)
Also if I am figuring out something OBO (off by one) prone sometimes I use this to double check myself: http://play.golang.org/
1. moving a break point
2. recompile
3. run
4. stopping at new break point
I think that happening behind the scenes could be made to appear like live editing in other languages. Go is fast enough compiling and fast enough executing that I think it could be pulled off as not appear laggy as well. But maybe I'm wrong and I don't understand well enough how LT handles other langs.It is an interactive process. You are build pieces of the application bit by bit.
There is no complete application state where to set breakpoints.
Yes, the Go people keep mentioning that. You might as well eat soy and pretend it's a delicious steak.
For people that have used good REPLs, from Lisp machines to iPython, it's not the same thing at all.
You lose your state, you loose context, you loose good introspection, etc etc. And if you try loading stuff that's big (several packages as dependencies etc), the compile time starts adding up too.
I know this is already done in any number of big enterprisey IDEs, but you would surely take a fresh and creative approach.
Go would be a perfect test candidate.
[1]: http://www.jacobsheehy.com/2013/03/living-in-the-future-star...
[2]: https://play.google.com/store/apps/details?id=com.aide.ui