Skip to content
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

Introduce ExecutionContext.opportunistic for use in apps #9296

Merged
merged 2 commits into from Nov 13, 2020

Conversation

viktorklang
Copy link
Contributor

@viktorklang viktorklang commented Oct 29, 2020

Introduces ExecutionContext.opportunistic as a private[scala] instance as an escape-hatch for getting the original 2.13.0 batching global EC

@viktorklang viktorklang added this to the 2.13.4 milestone Oct 29, 2020
Copy link
Member

@dwijnand dwijnand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, Viktor!

@viktorklang
Copy link
Contributor Author

@dwijnand You're most welcome! I added a MIMA exception since that errored out the build. Waiting for build confirmation of success.

@lrytz lrytz force-pushed the wip-opportunistic-√ branch 3 times, most recently from e433454 to 39edf7e Compare November 9, 2020 12:55
@lrytz
Copy link
Member

lrytz commented Nov 9, 2020

@viktorklang I changed the field to a lazy val and added a second commit with changes to Scaladocs. Let me know what you think.

…e as an escape-hatch for getting the original 2.13.0 batching global EC
@dwijnand dwijnand mentioned this pull request Nov 10, 2020
72 tasks
@dwijnand dwijnand added the release-notes worth highlighting in next release notes label Nov 10, 2020
@dwijnand dwijnand changed the title Introduces ExecutionContext.opportunistic as a private[scala] instanc… Introduce ExecutionContext.opportunistic for use in apps Nov 10, 2020
@lrytz
Copy link
Member

lrytz commented Nov 11, 2020

@viktorklang updated - lgty now?

@viktorklang
Copy link
Contributor Author

@lrytz LGTM

@lrytz
Copy link
Member

lrytz commented Nov 12, 2020

There is a remaining issue: private[x] members are skipped by scaladoc unless it runs with -private, which we don't for the library. So noone is going to be able to see these docs that we wrote 😕

Should we move/copy the documentation for opportunistic to global? Other suggestions?

@dwijnand
Copy link
Member

I'd say move and point opportunistic's docs to it.

@viktorklang
Copy link
Contributor Author

@dwijnand @lrytz Dale's suggestion looks sound to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes worth highlighting in next release notes
Projects
None yet
5 participants