We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've made a toy language: https://github.com/avwie/borklang
Everything works correctly on the JVM and when running jvmTest and jsTest. Also my web project is working correctly when I use browserDevelopmentRun.
jvmTest
jsTest
browserDevelopmentRun
However, when I use browserDistributionRun or make a web-distributable, the tokenizer/parsers don't work correctly.
browserDistributionRun
For instance:
fn fib = (n) -> { if (n < 2) n else fib(n - 1) + fib(n - 2) } fib(10)
This returns 55 in development mode, but in production mode I get: Invalid number format: 'fi'
Invalid number format: 'fi'
I found no way on how to debug this, because I loose a lot of information with productionRun.
The text was updated successfully, but these errors were encountered:
It's actually pretty easy to reproduce. Just pick the BooleanExpression demo and run it in a nodeJS target in production.
ParseException: Could not parse input: UnparsedRemainder(startsWith=id@2 for " &" at 1 (1:2))
So this library does not work in JS production environments.
Sorry, something went wrong.
Fixed in #67
No branches or pull requests
I've made a toy language: https://github.com/avwie/borklang
Everything works correctly on the JVM and when running
jvmTest
andjsTest
. Also my web project is working correctly when I usebrowserDevelopmentRun
.However, when I use
browserDistributionRun
or make a web-distributable, the tokenizer/parsers don't work correctly.For instance:
This returns 55 in development mode, but in production mode I get:
Invalid number format: 'fi'
I found no way on how to debug this, because I loose a lot of information with productionRun.
The text was updated successfully, but these errors were encountered: