-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Support a custom executor in StreamEffect #1483
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
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,6 @@ | ||
| package zio.stream | ||
|
|
||
| trait StreamEffectPlatformSpecific | ||
| trait StreamPlatformSpecific | ||
| trait ZStreamPlatformSpecific | ||
| trait ZSinkPlatformSpecific |
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
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.
As far as I can tell, this structure doesn't compose with well-defined semantics. Consider, e.g.
x ++ y— what is theexecutorfor such a composite?It seems like we need to say three things:
reserveof the managedreserveof managed (on finalization)effectBlockinginstead ofeffectTotal, etc.).So unless I'm missing something, we can do this w/o new machinery. Right? Or wrong? 😄
Uh oh!
There was an error while loading. Please reload this page.
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.
Say
x: StreamEffectuses a Blocking executor,y: StreamEffectuses a regular executor, andz: Streamthat is asynchronous.(x ++ y ++ z).processdoes the following:xand starts pulling it. ThePullonxevaluates the() => Athunk while locked to the Blocking executor (StreamEffect.scala:34), so that pull runs on the blocking executor;yand starts pulling it. Similarly, it evaluates the thunk while locked to the default executor, so that pull runs there.zand starts pulling it. ThatPulldoes whatever it wants because it's effectful.From how I'm reading things, the semantics here are identical to the semantics of
lock, as long as we always propagate the executor when composingStreamEffectvalues. Wdyt?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.
@jdegoes
Sorry, I realized I didn't respond to your questions about whether it's possible to do this without new machinery.
The problem is as follows: how does a constructor (like
fromInputStream), which only produces a thunkManaged[E, () => A], indicate that when a stream which is based on it is run, it should be run on the Blocking threadpool? We can't useeffectBlockingbecause we want to produce synchronous code that runs in the thunk.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.
@jdegoes Any thoughts on the above? :-)
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.
I was busy with the huge
ZSinkrewrite PR, where are we with this?@iravid @jdegoes
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.
We hashed it over deadlift sets. I believe @jdegoes is onboard. I'll pick this back up next week :-)
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.
Awesome. Please keep me in the review loop.