diff options
| author |  Abseil Team <absl-team@google.com> | 2023-01-11 15:06:02 -0800 |
|---|---|---|
| committer |  Copybara-Service <copybara-worker@google.com> | 2023-01-11 15:07:05 -0800 |
| commit | 0db27008fbd44253e428298cda58f6c8f56134f5 (patch) | |
| tree | ce446aeac026723b59552d1a99740e17d84e4c71 /absl/random/seed_gen_exception.cc | |
| parent | 570dc02b0b70bd4fb37efd79021890fa9edc283f (diff) | |
Improve BitGen stability documentation
Several problems with the previous documentation:
* It said it's stable "within the same binary" but not stable "across multiple binary invocations". Those statements contradict each other.
* It said "in the same binary will not produce the same sequence of variates within the same binary", which is repetitive since it says "in the same binary" twice.
* The comments about the seed sequence were not all next to each other, they were split apart by a rand.req.urng comment.
* It implied that process stability is all you get, whereas generally you also get changelist stability.
* It said you can use a seed sequence with SharedBitGen, but you can't.
* It said there is more info in std_seed_seq.h , but there isn't.
PiperOrigin-RevId: 501389708
Change-Id: I5e3dbc3548cc051265b8d004191c23147eccecc3
Diffstat (limited to 'absl/random/seed_gen_exception.cc')
0 files changed, 0 insertions, 0 deletions