Move legacy thread proxying system into seperate source and header. NFC #19946
+724
−686
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sbc100
changed the title
sbc100
force-pushed
the
rename_proxying_func
branch
from
b8a3ecd to
9c78fda
Compare
tlively
approved these changes
Aug 1, 2023
This is the first step towards removing the internal use of the old proxying system. The primary user of which is the JS library proxying system. The legacy proxying system is already layered on top of the new proxying system so removing it should be pure win.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the first step towards removing the internal use of the old proxying system. The primary user of which is the JS library proxying system.
The legacy proxying system is already layered on top of the new proxying system so removing it should be pure win.