-
Notifications
You must be signed in to change notification settings - Fork 685
Add ChannelPipeline.SynchronousOperations.Position #3065
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
@Lukasa I've updated the existing public APIs to use the new type to avoid confusing the compiler since the APIs are not usable in their current form. It you'd prefer all the existing APIs to be deprecated and add |
Thanks Tim. Yeah, can we use overloads and |
Updated - I was getting compiler errors due to "ambiguous references..." without the disfavoured overloads so added them in |
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.
Thanks for this! I've left a few notes in the diff.
@Lukasa all these should be fixed now |
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.
Ok great, this looks really good. One quick note though, can we add a few very simple tests of these new APIs? Just inserting handlers and confirming they're there is sufficient.
Yes that would be helpful - added! |
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.
Ok, this LGTM. Let's see what CI says.
Looks like the format check wants some cleanups, mind tackling that for me? |
Done |
Adds a new
ChannelPipeline.SynchronousOperations.Position
type to fill a hole in the API that prevented non-sendable Channel handlers being added at a position to the pipeline via the synchronous operations.