[stdlib] Remove RNG's next extension methods from public interface #19551
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.
This is currently pending core team approval/evolution review. Evolution Post and Evolution PR
The generic version of
next<T>() -> Twas causing an issue where implementers ofRandomNumberGeneratorwere not required to writenext() -> UInt64requirement. This patch removes both the extension methods onRandomNumberGeneratorfrom public interface (I actually removednext<T>() -> Tbecause it was a one-liner forT._random(using:).) Users are encouraged to write somewhat more meaningful code likeInt.random(in: 0 ..< 10, using: &generator).Resolves: SR-8758
cc: @airspeedswift @stephentyrone