-
Notifications
You must be signed in to change notification settings - Fork 41
Remove methods have been obsolete over two decades #168
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
|
The |
Partially revert ruby#168 because strscan_rest_p did not have rb_warning("StringScanner#rest? is obsolete"). It is actively used by the latest tzinfo.gem, and we shouldn't remove it without deprecating it.
Partially revert #168 because strscan_rest_p did not have `rb_warning("StringScanner#rest? is obsolete")`. It is actively used by the latest tzinfo.gem, and we shouldn't remove it without deprecating it.
(ruby/strscan#169) Partially revert ruby/strscan#168 because strscan_rest_p did not have `rb_warning("StringScanner#rest? is obsolete")`. It is actively used by the latest tzinfo.gem, and we shouldn't remove it without deprecating it. ruby/strscan@f3fdf21189
It wasn't marked "obsolete" in the first place, so I pushed a partial revert #169 to fix a ruby/ruby CI. |
(ruby/strscan#169) Partially revert ruby/strscan#168 because strscan_rest_p did not have `rb_warning("StringScanner#rest? is obsolete")`. It is actively used by the latest tzinfo.gem, and we shouldn't remove it without deprecating it. ruby/strscan@f3fdf21189
No description provided.