Skip to content
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

Parse statements with or_continue and or_break #382

Closed
thetarnav opened this issue May 5, 2024 · 3 comments
Closed

Parse statements with or_continue and or_break #382

thetarnav opened this issue May 5, 2024 · 3 comments

Comments

@thetarnav
Copy link
Contributor

It seems that or_else and or_return are supported, but not or_continue and or_break.
(no semantic tokens/go to definition/hover)
Which is understandable as they were added recently.
I'm guessing it should be a simple change to parse them.

@DanielGavin
Copy link
Owner

DanielGavin commented May 5, 2024

Are we talking about the formatter? Is the ast already in core:odin/parser?

@thetarnav
Copy link
Contributor Author

thetarnav commented May 5, 2024

no, about ols, is it really not in ast?
From looking at the ast package there is Or_Branch_Expr node and Token_Kind.Or_Break and Token_Kind.Or_Continue
And there is some code in the parser for creating those ...added 7 months ago.

@DanielGavin
Copy link
Owner

It seems it is. Fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants