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

[server] add range_clause highlight #9

Merged
merged 1 commit into from
Jan 10, 2024
Merged

[server] add range_clause highlight #9

merged 1 commit into from
Jan 10, 2024

Conversation

Lycs-D
Copy link
Contributor

@Lycs-D Lycs-D commented Jan 9, 2024

No description provided.

Comment on lines +50 to 54
} else if node.type_name == .range_clause {
if first_child := node.first_child() {
result << element_to_semantic(first_child, .property)
}
} else if node.type_name == .struct_field_declaration {
Copy link
Member

@spytheman spytheman Jan 10, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm, it may be better to change that else if ladder, to an exhaustive match?

@spytheman spytheman merged commit 1814be2 into vlang:main Jan 10, 2024
12 checks passed
@Lycs-D Lycs-D deleted the add_range_clause_highlight branch January 10, 2024 18:58
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

Successfully merging this pull request may close these issues.

2 participants