Draft: Use new rng in more places#317
Open
JamesMcClung wants to merge 4 commits intopsc-code:mainfrom
Open
Conversation
JamesMcClung
force-pushed
the
pr/use-rng
branch
from
7de2323 to
8936866
Compare
JamesMcClung
force-pushed
the
pr/use-rng
branch
from
8936866 to
8270b02
Compare
added 4 commits
June 16, 2025 09:26
could be further streamlined This changes the behavior of RngC: it can now return 0 instead of 1. However, it seems like this is actually the correct behavior.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Transition away from using random(). Needs more testing.