-
-
Notifications
You must be signed in to change notification settings - Fork 15
Moonscript Support? #322
Comments
I'm not sure what the benefit would/could be? In your include example it doesn't save any configuration-option, or simplify the syntax to any useful extent. (I must admit I've never looked at moonscript before, I might be missing something obvious.) |
More thinking from the user side of things, moonscript does tend to be somewhat popular, and compiles cleanly, so why not let the user use it? But some things that a user might like are probably:
So if I were to go further with the incredibly contrived example:
|
If it were a new project I think that argument would be more compelling. As things stand 100% of the core, and user-scripts, are pure lua. Users are familiar with it, and it works well. There might be nice things, but changing just to gain string interpolation seems like a step too far. Your sample could be just as easily a table in the current setup, obviously. But I appreciate that is contrived example. I think I'll say |
I'm not suggesting a switch, or much changed behaviour. Basically avoid adding this to my own config.lua Something like:
If a user wants to use moonscript, then they probably know what it is, and as it compiles to Lua, the API doesn't change. |
Moonscript makes writing Lua a lot less boilerplate-y.
Would support be possible at all?
Something like if a *.moon file is found in the usual directories, and moonc is in $PATH, try and compile them to Lua. (Probably only at launch).
Quick contrived example:
As opposed to:
The text was updated successfully, but these errors were encountered: