Michał Zochniak
Michał Zochniak
Hm, so I don't think I understand the forking completely. Couldn't it just work on current commit in current git repository?
I'd still like to revisit the idea of keeping compiled files in separate branch, but maybe that's for later - I'm not sure how this could be done right now....
There should probably be a script to help with merges with mainline as well, what do you think?
So the additional source file would specify iced version number (single number, the `IcedCoffeeScript.patch`). But where would the CoffeeScript version be obtained from?
Oh, right. Thanks
I can have a try with this once https://github.com/keybase/go-crypto/pull/40 is done
Looks like the lexer has changed a bit, and the strings are parsed differently now in CoffeeScript. ``` coffee -t -e "\"#{2}/\"" [STRING_START (] [( (] [NUMBER 2] [) )]...
`iced3` is already on the new grammar/lexer so it works there.
It is still work in progress, unfortunately. You can follow this PR if you are interested: https://github.com/maxtaco/coffee-script/pull/168
@vird may I ask what's your use case? Would you be able to test new `iced3`, even by just installing it in test environment and running your application's test suite...