Skip to content

[5.5] We don't need the unavailable default implementation of RNG.next() to… #38273

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

Conversation

stephentyrone
Copy link
Contributor

Cherry-pick of #38272 for 5.5. Note that if we do not take this for some reason, we also will need to back that change out from main.

… be ABI.

Make it @_aEIC so that we're not stuck with it forever if we get a better solution someday.
@stephentyrone stephentyrone requested a review from a team as a code owner July 6, 2021 12:19
@stephentyrone
Copy link
Contributor Author

@swift-ci please test

@stephentyrone stephentyrone changed the title We don't need the unavailable default implementation of RNG.next() to… [5.5] We don't need the unavailable default implementation of RNG.next() to… Jul 6, 2021
@stephentyrone stephentyrone merged commit 81cd8ce into swiftlang:release/5.5 Jul 6, 2021
@stephentyrone stephentyrone deleted the unavailable-defaults-dont-need-to-be-abi-5.5 branch July 6, 2021 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants