Skip to content

programming model:task.futureResult not bound to desired EL if .delegate(on:) is specified #199

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

Closed
weissi opened this issue Apr 5, 2020 · 1 comment · Fixed by #241
Closed
Assignees
Labels
kind/bug Feature doesn't work as expected.
Milestone

Comments

@weissi
Copy link
Contributor

weissi commented Apr 5, 2020

Again, I'm not 100% sure if this counts as a bug but I think it should. If I set my EventLoopPreference to .delegate(on: desiredEL), then I probably want everything to happen on desiredEL.

I would argue that all the user-visible things that are important for the programming model should then happen on desiredEL. Mainly:

@weissi weissi added the kind/bug Feature doesn't work as expected. label Apr 6, 2020
@artemredkin artemredkin added this to the 1.2.0 milestone Apr 26, 2020
@weissi
Copy link
Contributor Author

weissi commented May 14, 2020

Same comment as on #200:

After a chat with @ktoso, I noticed that this ticket isn't clear enough. The rules should be:

All callouts (delegate, futures, callbacks, ...) AHC makes to the user should be on the preferred EL, no matter where the Channel lives
All callins (returned futures, callins, ...) from the user must be tolerated on any thread.
IMHO fixing this issue is blocking 1.2.0, we cannot possibly release it as on master as it's impossible to use right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Feature doesn't work as expected.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants