-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Performance #170
Performance #170
Conversation
# In case we're running on an older Ruby version, we polyfill it here. | ||
unless :+.respond_to?(:name) | ||
class Symbol # rubocop:disable Style/Documentation | ||
def name |
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.
Hum, that polyfill might trick other gems or code into thinking they are on 3.0. Have you considered using a refinement here? I generally avoid them like the plague, but for unobstrusive polyfill I found them relatively useful.
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.
Ahh yeah I can make it a refinement.
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.
Turns out I stopped using it in as many places as I thought, this is much better now
No description provided.