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
but it should eval to "a string" observed in workspace and in direct usage
3 +"a string" eval correctly to "3a string"
The text was updated successfully, but these errors were encountered:
@onsetsu any ideas?
Sorry, something went wrong.
Having a single String in a file is actually interpreted as a directive, e.g. used to activate strict mode:
"use strict";
We could recognize such cases explicitly during transpilation.
I also found that simply evaluating {a:1} returns undefined rather than the expected object.
{a:1}
undefined
Maybe there is a deeper problem with literals.
({a:1}) seems to be fine and ("hello") works also fine.
those two cases are relatively important during interactive workspace sessions....
I also found that simply evaluating {a:1} returns undefined rather than the expected object. Maybe there is a deeper problem with literals.
Well, actually this is not an ObjectExpression but a BlockStatement with a LabelStatement.
ObjectExpression
BlockStatement
LabelStatement
So it returns undefined.
No branches or pull requests
but it should eval to "a string"
observed in workspace and in direct usage
3 +"a string" eval correctly to "3a string"
The text was updated successfully, but these errors were encountered: