Skip to content

Conversation

hvitved
Copy link
Contributor

@hvitved hvitved commented Dec 14, 2021

The various Pattern classes got introduced before we supported pattern matching, as a common way of describing destructured assignments and destructured parameters. Now, however, they give more rise to confusion (they have nothing to do with pattern matching) than benefit, so I think we should simply deprecate them.

I also fixed a bug in the computation of callables belonging to nested destructured parameters.

@github-actions github-actions bot added the Ruby label Dec 14, 2021
@hvitved hvitved force-pushed the ruby/deprecate-pattern-classes branch from b202691 to e882cda Compare December 14, 2021 14:05
@hvitved hvitved marked this pull request as ready for review December 14, 2021 14:33
@hvitved hvitved requested a review from a team as a code owner December 14, 2021 14:33
@nickrolfe
Copy link
Contributor

A couple of trivial questions, but otherwise this looks very sensible.

@hvitved
Copy link
Contributor Author

hvitved commented Dec 15, 2021

A couple of trivial questions, but otherwise this looks very sensible.

I don't see any questions?

@nickrolfe
Copy link
Contributor

A couple of trivial questions, but otherwise this looks very sensible.

I don't see any questions?

Sorry, you should see them now. I was reviewing from VS Code, but the extension seems very flaky when it comes to submitting reviews.

Copy link
Contributor

@nickrolfe nickrolfe left a comment

Choose a reason for hiding this comment

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

LGTM

@hvitved hvitved merged commit e9ef53c into github:main Dec 16, 2021
@hvitved hvitved deleted the ruby/deprecate-pattern-classes branch December 16, 2021 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants