-
-
Notifications
You must be signed in to change notification settings - Fork 35
"select" in variable name confuses parser #149
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
Comments
Same thing happens to me. Came here to report the same issue |
That's my bad 👎 ... I made a change when trying to generalize the |
@pedro-ricardo Any updates? |
I'm sorry @kc9jud , but my job is currently consuming all the time I've got. So I still haven't look into this, and to be honest it's way down on my priorities. |
No worries -- I was considering trying to come up with a PR, but I wanted to make sure you weren't already working on it. |
### Check List - Highlight - [x] `select` keyword - *Merge #165 to fix #149* - [x] `rank` keyword - *Merge #165* - [x] `forall` keyword - *Merge #170 to fix #169* - Symbol List - [x] Symbols bug in VSCode +1.40 - *Merge #161 to fix #154* - [x] Symbols classification - *Merge #141 to fix #140* - [x] Long named symbols - *Merge #151* - Settings - [x] Add more options - *Merge #152* - Dependencies - [x] Merge `dependabot` PR's - [x] lodash - *Merge #144* - [x] mixin-deep - *Merge #146* - [x] handlebars - *Merge #155* - Code Completion - [x] Array constructor - *Fix #148* - New Features - [x] Breakpoints - *Merge #150*
Opening a file which contains a variable with
select
in the name appears to crash/confuse the parser:with variable commented out:

The text was updated successfully, but these errors were encountered: