-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Exclamation point is not considered a valid symbol for function name #156
Comments
Thank you for report, Will be fixed in next release |
I encountered a problem due to which I had to change the behavior of the lexer and parser, namely how the AST tree is built for ModifyExpression But I hope to finish this soon, and the behavior of identifiers will be exactly the same as in the original FunC compiler. Thank you and stay tuned |
### Added - Language selection in project template ([#148](#148)) - Empty and example project templates ([#147](#147)) - `#include` assist ([#108](#108)) ### Fixed - Negative method IDs are considered a syntax error ([#157](#157)) - Non-ASCII characters in FunC identifiers ([#156](#156)) - Invalid trailing comma in return tuple type ([#155](#155)) - Unresolved reference to uninitialized variable ([#151](#151)) - Invalid indent for multiline tuples in function signature return type ([#150](#150)) - Auto-complete not work on `slice~` ([#149](#149)) - `method_id` completion ([#126](#126)) - Reference resolving with identifiers containing non-letter characters ([#107](#107)) - Uppercase HEX in TL-B ([#100](#100)) - Indent in chain calls ([#38](#38))
Fixed in 2.1.0 |
The highlighter considers that
!
cannot be used in function name.While in reality it is perfectly fine and the code works.
Using the latest v2.0.4 plugin.
The text was updated successfully, but these errors were encountered: