Changes to seeded RNG #1
Open
Conversation
This file contains 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
|
Don't merge this yet. I have some stuff coming that I need to commit. |
|
It should be good to merge now. |
|
i need to check a bit of code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Some changes to random number generation.
Importantly, there's now a notion of a "seeded sequence". This sequence always starts at the same place for a given seed but it continues onward for as many calls as needed.
Description
HQ_RANDOM is also now supported, using a different stream for seeded numbers.
Chaos mode works slightly differently. If allowed, it instead modifies the input seed with a random value. The difference should be close to unnoticeable in practice.
As a side effect, some extra whitespace was removed as well. Oops.
Feature(s) this PR does NOT handle:
None.
Discord contact info
tertu