You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since I have been using CoffeeScript for a long time, there are some practice that I think maybe some of them fit igo too.
In CoffeeScript, running coffee enters interactive mode there's another igo for that. But for Go, repl might be less useful.
When a user runs coffee file.coffee, code in that file is evaluated directly, just like it's just a language and steps of debugging does not contain something like "convert it to another language".
Putting .js and .coffee file side by side is quite painful when the projects get larger. Because theres a lot of changes people click by mistake.
I suppose igo run would make it a lot simpler for people to use igo.
The text was updated successfully, but these errors were encountered:
Since I have been using CoffeeScript for a long time, there are some practice that I think maybe some of them fit igo too.
coffee
enters interactive mode there's another igo for that. But for Go, repl might be less useful.coffee file.coffee
, code in that file is evaluated directly, just like it's just a language and steps of debugging does not contain something like "convert it to another language"..js
and.coffee
file side by side is quite painful when the projects get larger. Because theres a lot of changes people click by mistake.I suppose
igo run
would make it a lot simpler for people to use igo.The text was updated successfully, but these errors were encountered: