-
Notifications
You must be signed in to change notification settings - Fork 184
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
nest-match=align now works with match%ext. #2648
Conversation
Why does the linux build fail because of lacking sudo priviledges ? I had hoped to see the result of test-branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks! The CI is having difficulties, can you rebase on top of #2649 ?
({pexp_desc= Pexp_match _ | Pexp_try _; pexp_loc; _}, _) | ||
} ] ) | ||
, `Align ) | ||
when Source.extension_using_sugar ~name:ext ~payload:pexp_loc -> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function is used quite often, at some point we could consider putting this information in the Pexp_extension
node.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes of course, but that turns a simple patch into a complicated project. I don't think my employer would be willing to let me do it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm mentioning this in case it spawns ideas. Of course, I want this fix to go in first.
6368226
to
b901525
Compare
I think this is good to go |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No diffs with test-branch, let's merge!
match%ext used to not be treated the same by nest-match-align. This is now fixed.
Requested in Issue #2081
Seems to be a very lightweight patch, and that the bug was not present at all in the test base.