)]}'
{
  "commit": "0db27008fbd44253e428298cda58f6c8f56134f5",
  "tree": "ce446aeac026723b59552d1a99740e17d84e4c71",
  "parents": [
    "570dc02b0b70bd4fb37efd79021890fa9edc283f"
  ],
  "author": {
    "name": "Abseil Team",
    "email": "absl-team@google.com",
    "time": "Wed Jan 11 15:06:02 2023 -0800"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Wed Jan 11 15:07:05 2023 -0800"
  },
  "message": "Improve BitGen stability documentation\n\nSeveral problems with the previous documentation:\n\n* It said it\u0027s stable \"within the same binary\" but not stable \"across multiple binary invocations\". Those statements contradict each other.\n* 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.\n* The comments about the seed sequence were not all next to each other, they were split apart by a rand.req.urng comment.\n* It implied that process stability is all you get, whereas generally you also get changelist stability.\n* It said you can use a seed sequence with SharedBitGen, but you can\u0027t.\n* It said there is more info in std_seed_seq.h , but there isn\u0027t.\n\nPiperOrigin-RevId: 501389708\nChange-Id: I5e3dbc3548cc051265b8d004191c23147eccecc3\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "71b6309288e66c560d7e1d9de8da7c88337ad3ed",
      "old_mode": 33188,
      "old_path": "absl/random/random.h",
      "new_id": "767208671c1481de4d2277e1c40fde57fc3df53d",
      "new_mode": 33188,
      "new_path": "absl/random/random.h"
    }
  ]
}