There is no documentation that says zero isn't okay, and the closed interval [0, k] described by the documentation is perfectly well-defined even when k is zero. As far as I can tell, there is no reason *not* to support zero: a random variable that always returns the same value is still a random variable. absl::Uniform will happily generate on the interval [0, 1) for the same reason. PiperOrigin-RevId: 694649518 Change-Id: Ib940406f762a30e27c19c846c45bd908ae8411c3
| Name |
Last commit
|
Last Update |
|---|---|---|
| .github | Loading commit data... | |
| CMake | Loading commit data... | |
| absl | Loading commit data... | |
| ci | Loading commit data... | |
| .clang-format | Loading commit data... | |
| .gitignore | Loading commit data... | |
| ABSEIL_ISSUE_TEMPLATE.md | Loading commit data... | |
| AUTHORS | Loading commit data... | |
| BUILD.bazel | Loading commit data... | |
| CMakeLists.txt | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| FAQ.md | Loading commit data... | |
| LICENSE | Loading commit data... | |
| MODULE.bazel | Loading commit data... | |
| PrivacyInfo.xcprivacy | Loading commit data... | |
| README.md | Loading commit data... | |
| UPGRADES.md | Loading commit data... | |
| WORKSPACE | Loading commit data... | |
| WORKSPACE.bzlmod | Loading commit data... | |
| conanfile.py | Loading commit data... | |
| create_lts.py | Loading commit data... |