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.

Sign up for GitHub

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

Jump to bottom

Don't double-invoke effects in legacy roots #20028

Merged
merged 1 commit into from
Oct 15, 2020
Merged

Don't double-invoke effects in legacy roots #20028

merged 1 commit into from
Oct 15, 2020

Commits on Oct 14, 2020

  1. Don't double-invoke effects in legacy roots 

    Large legacy applications are likely to be difficult to update to handle this feature, and it wouldn't add any value– since newer APIs that require this resilience are not legacy compatible.
    Brian Vaughn committed Oct 14, 2020
    Configuration menu
    Copy the full SHA
    43eab00 View commit details
    Browse the repository at this point in the history