-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
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
FEATURE: Simplify template literals #33
Comments
I think it’s like pythons f strings, except the f ^^ - so yes I like it ;) also the ${ is less intuitive to write than a simple brace |
i like phps behaviour of nowdocs better, there the indentation of the closing defines where each line starts |
Like this?:
|
yes. taken from the php doc:
output:
|
Agreed. I adjusted the issue description accordingly. |
I'm currently trying:
nvm... There needs to be an alternative to handling ambiguous tokens anyway, so |
As of right now, template literals are modeled after ECMAScript, e.g.:
Imho this causes two problems:
${
sequence is a considerable complication for the parser (or better: The tokenizer)trim
ed away by the engine itselfI therefore suggest to change the template literal syntax to this:
Rules are:
This will still allow for possible future tagged template literals, like:
The text was updated successfully, but these errors were encountered: