-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Clarify upgrade path for Regex.regex?
(#12785)
#12786
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
Conversation
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.
Wdyt about the term
term? 🙃
Co-authored-by: Andrea Leopardi <an.leopardi@gmail.com>
Co-authored-by: Andrea Leopardi <an.leopardi@gmail.com>
@whatyouhide sounds perfect! Thanks for the suggestions, which I have applied. |
Co-authored-by: Andrea Leopardi <an.leopardi@gmail.com>
@whatyouhide we could go further and add this, equally useful: What do you think? |
@thbar I personally don't see the reason for using |
@whatyouhide ok, one upgrade path is enough in that case anyway! |
💚 💙 💜 💛 ❤️ |
Merged and backported! |
This addresses:
Regex.regex?/1
#12785Pending questions:
term
is perfect