)]}'
{
  "commit": "37ece9cf9bcfd9587d584a757f5073731ce5a2d5",
  "tree": "35af117732d5a6f99fe05dee160c9058dce77f2a",
  "parents": [
    "c4a254f7f33967b469d4104be27c8e2a17bf0d03",
    "3387a58bc777d31493f37160cdd1f57223f0bc0c"
  ],
  "author": {
    "name": "Stuart Cook",
    "email": "Zalathar@users.noreply.github.com",
    "time": "Tue Feb 03 21:58:39 2026 +1100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Feb 03 21:58:39 2026 +1100"
  },
  "message": "Rollup merge of #151109 - tyhdefu:float_bits_const, r\u003dtgross35\n\nfN::BITS constants for feature float_bits_const\n\nAlso enables the feature for compiler_builtins as otherwise this causes a warning and conflicts with the Float extension trait.\n\n---\nImplementation for rust-lang/rust#151073\n\nFeature flag: `#![feature(float_bits_const)]`\n\nNote that this is likely to conflict with some extension traits, as it has with compiler builtins. However, assuming correct values for the constants, they are either `u32`, the same type, which should not cause a problem (as shown by enabling the feature for compiler_builtins), or a different type (e.g. `usize`), which should cause a compiler error. Either way this should never change behaviour unless the extension trait implemented an incorrect value.\n\nAlso note that it doesn\u0027t seem to be possible to put multiple unstable attributes on an item, so `f128::BITS` and `f16::BITS` are gated behind the feature flags for those primitives, rather than `#![feature(float_bits_const)]`\n",
  "tree_diff": []
}