Earlier quoted context omitted.
You know, I looked into this briefly and based on the way go works, it's not clear to me how useful it would be. Go doesn't really have a good REPL, which is an indication. If there was a decent way to handle dynamic evaluation though, it could certainly be added, and without too much issue I would imagine :)
Go compiles so fast you can just pretend there is dynamic eval. People sometimes use the "go run" command to compile and run Go source in one operation, that is not really too different from just invoking an interpreter. Go provides a lot of tools to parse Go source, I imagine between that, Go's fast compiler and GDB support it wouldn't be as hard as many compiled langs to support. Also if I am figuring out something…
Light Table 0.4 released
21–30 of 193 posts
Re: Light Table 0.4 released
#22Earlier quoted context omitted.
You know, I looked into this briefly and based on the way go works, it's not clear to me how useful it would be. Go doesn't really have a good REPL, which is an indication. If there was a decent way to handle dynamic evaluation though, it could certainly be added, and without too much issue I would imagine :)
Go compiles so fast you can just pretend there is dynamic eval. People sometimes use the "go run" command to compile and run Go source in one operation, that is not really too different from just invoking an interpreter. Go provides a lot of tools to parse Go source, I imagine between that, Go's fast compiler and GDB support it wouldn't be as hard as many compiled langs to support. Also if I am figuring out something…
Re: Light Table 0.4 released
#23I dream of the day Light Table has Go support.
You know, I looked into this briefly and based on the way go works, it's not clear to me how useful it would be. Go doesn't really have a good REPL, which is an indication. If there was a decent way to handle dynamic evaluation though, it could certainly be added, and without too much issue I would imagine :)
Re: Light Table 0.4 released
#24Earlier quoted context omitted.
Go compiles so fast you can just pretend there is dynamic eval. People sometimes use the "go run" command to compile and run Go source in one operation, that is not really too different from just invoking an interpreter. Go provides a lot of tools to parse Go source, I imagine between that, Go's fast compiler and GDB support it wouldn't be as hard as many compiled langs to support. Also if I am figuring out something…
The big difference is that you lose state every time you do that, the main goal with the eval in LT is to prevent that :)
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.Re: Light Table 0.4 released
#25I can only hope for eventual PHP integration so it's useful to me also at work.
Re: Light Table 0.4 released
#26Also my "return" is not updated automaticall.
Re: Light Table 0.4 released
#27Re: Light Table 0.4 released
#28Re: Light Table 0.4 released
#29Is there a way to have it evaluate all the Python in my file so I don't have to go and manually evaluate each function? Also my "return" is not updated automaticall.
Re: Light Table 0.4 released
#30Now that source maps are in CoffeeScript, any chance of future support? Also, vim bindings?
Use the "Vim: Toggle vim mode" command from the command tab.