Yin Zhong

Can confirm same problem (and workaround) on Windows 10 + {PowerShell, Git Bash}.

Thanks. Confirmed that `endian="msb"` together with `to_be_bytes` gives the correct result. However, if the library is truly endianness agnostic, why does it not work if `endian="lsb"` is used together with...

不需要`\n`，因为钦定了

Unfortunately this is likely to be a by-product of the proposed Babel-based toolchain (#862), even though the effort appears to be stalled at the moment.

I used the nightly MSI installer. For now I am manually byte-swapping... will try again when the `#include` fix is included in the next release.

[This test](https://github.com/gkz/LiveScript/blob/master/test/loop.ls#L389) ``` livescript # Closure-wrapped comprehensions that refer to the "arguments" object expr = -> result = [item * item for item in arguments] ok expr(2, 4, 8).join(' ')...

I'm gonna try land #823 first, then think about this.

@vendethiel Why? Sure #823 is about something different, namely `(yield ...)` could evaluate to a function. My worry is these two might clash and not merge cleanly, so I want...

Ah I get you now. It's ambiguous what it pipes into. My concern is you cannot treat `yield` as just another function (otherwise you would have to write `yield!`)...

Decorators are still under development in ECMAScript proper.