Skip to content

allow explicit ExecutionContext #21

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
nairbv opened this issue Jun 13, 2013 · 1 comment
Closed

allow explicit ExecutionContext #21

nairbv opened this issue Jun 13, 2013 · 1 comment
Milestone

Comments

@nairbv
Copy link

nairbv commented Jun 13, 2013

As mentioned at scala days, it would be nice to be able to explicitly pass an ExecutionContext.

retronym added a commit to retronym/async that referenced this issue Jul 2, 2013
 - Avoid reset + retypecheck, instead hang onto the original types/symbols
 - Eliminated duplication between AsyncDefinitionUseAnalyzer and ExprBuilder
   - Instead, decide what do lift *after* running ExprBuilder
   - Account for transitive references local classes/objects. Still a few issues
     with the way we lift them, so the restrictions haven't been removed yet.
 - Make the execution context an regular implicit parameter of the macro
 - Fixes interaction with existential skolems and singleton types

Fixes scala#6, scala#13, scala#16, scala#17, scala#19, scala#21.
retronym added a commit to retronym/async that referenced this issue Jul 3, 2013
 - Avoid reset + retypecheck, instead hang onto the original types/symbols
 - Eliminated duplication between AsyncDefinitionUseAnalyzer and ExprBuilder
   - Instead, decide what do lift *after* running ExprBuilder
   - Account for transitive references local classes/objects and lift them
     as needed.
 - Make the execution context an regular implicit parameter of the macro
 - Fixes interaction with existential skolems and singleton types

Fixes scala#6, scala#13, scala#16, scala#17, scala#19, scala#21.
@phaller
Copy link
Contributor

phaller commented Aug 14, 2013

Fixed in #27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants