Summer Knight

Results 61 issues of Summer Knight

Currently a license comment like `/*! blah */` is output after the helpers, and it shouldn't be as long as it's the first thing in the source.

If a macro were aware that it were being assigned to an immutable variable or being returned, then it could not make `tmp` variables e.g. ``` let q = for...

It could be handy to have a tutorial with a REPL that teaches the user how to code in GorillaScript.

It would be handy for code examples to not have a million helpers splayed at the top, but still know which ones were used. Also, this could somehow be used...

It could be useful to be able to parse "GSON", which would be a superset of JSON except that it supports GorillaScript syntax instead. Could be handy for configuration files....

Currently `-x^y` parses as `(-x)^y` rather than `-(x^y)`, which is the mathematically correct one.

One could enable no-indent mode, for example by sticking a /*gorilla noindent: true */ either at the top of a file or immediately following the #!shebang.

Currently the public-facing API calls such as GorillaScript.compile are black boxes due to a documentation shortage. They need to be documented and probably made more friendly in the process.

documentation

GorillaScript has a way to compile text files with embedded GorillaScript code in them, similar to the way PHP works with its `` tags. [egs](https://github.com/ckknight/egs) wraps up GorillaScript's rather dumb...

documentation

Since generators are going into V8, once node supports them in the current version, there should be a way to have GorillaScript compile ES6-syntax generators instead of the state machines...