-
-
Notifications
You must be signed in to change notification settings - Fork 378
no more RBScanner errorBlock #12900
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
no more RBScanner errorBlock #12900
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.
Good!
Failing test that maybe realted: BCBeautifulCommentsSettingsTest>>testRenderingOfMyOwnComment CI problem not related:
|
Moved back old code as No-op to ease the loading :( My assumption is that old compiled methods in fresh image are still using the killed API, but the RBScanner methods are moved/removed before such client method are updated (and recompiled). Now I can reproduce the BCBeautifulCommentsSettingsTest issue, I will investigate. |
Yes, I think so... code loading is not atomic sadly |
I think it was a syntactic error in the depreciation clause (so the method just failed). |
PR #12892 removed the last usage of errorBlock in RBScanner.
This PR does the almost final cleanup of now unused code.
Because existing images still refer to some undead method of RBScanner (
on:errorBlock:
anderrorBlock:
) they are kept as empty shells.Note: for some reason, moving these two methods as extension methods in Deprecated11 also break Iceberg. Possible the "move" is not atomic so the removal of the method in AST-Core is done before it is added in Deprecated11 letting the low level code experiences MNU errors.