Skip to content

Fixing regression introduced by #3310 with missing word boundary #3891

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.

Sign up for GitHub

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

Jump to bottom
Merged
JoeKar merged 1 commit into from
Oct 19, 2025
Merged

Fixing regression introduced by #3310 with missing word boundary #3891

JoeKar merged 1 commit into from
Oct 19, 2025

Conversation

@Neko-Box-Coder
Copy link
Contributor

@Neko-Box-Coder Neko-Box-Coder commented Oct 17, 2025 •
edited
Loading

Fixing regression introduced by #3310 with missing word boundary

Test cases (I like how github isn't highlighting some of these properly):

456'456.
.13248'4456
0x.456'45
58.
4e2
123.456e-67
123.456e-67f
.1E4f
0x10.1p0
0x1p5
0x1e5
3.14'15'92
1.18e-4932l
3.4028234e38f
3.4028234e38
3.4028234e38l

enum enumeration {
    VALUE_0 = 0
    value_1 = 1
    VALUE_LAST = value_1
} enumeration_t;

@JoeKar

@JoeKar JoeKar merged commit 115e560 into zyedidia:master Oct 19, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@JoeKar JoeKar JoeKar approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Neko-Box-Coder @JoeKar