aboutsummaryrefslogtreecommitdiff
path: root/src/kernel/mempool_limits.h
diff options
context:
space:
mode:
authorAva Chow <github@achow101.com>2024-05-03 12:36:56 -0400
committerAva Chow <github@achow101.com>2024-05-03 12:36:56 -0400
commitf5b6f621fff7540ca97974b26a66ca1cc6db018c (patch)
tree911c114e6f8b7bb9ef2ba71831f5f22b8bba0d06 /src/kernel/mempool_limits.h
parentf9486de6a96b624982a2d45b895bfe4e865063d1 (diff)
parentffc674595cb19b2fdc5705b355bdd3e7f724b860 (diff)
Merge bitcoin/bitcoin#30024: doc: replace remaining "520" magic nums with MAX_SCRIPT_ELEMENT_SIZE
ffc674595cb19b2fdc5705b355bdd3e7f724b860 Replace remaining "520" magic numbers with MAX_SCRIPT_ELEMENT_SIZE (Jon Atack) Pull request description: Noticed these while reviewing BIPs yesterday. It would be clearer and more future-proof to refer to their constant name. ACKs for top commit: instagibbs: ACK ffc674595cb19b2fdc5705b355bdd3e7f724b860 sipa: ACK ffc674595cb19b2fdc5705b355bdd3e7f724b860 achow101: ACK ffc674595cb19b2fdc5705b355bdd3e7f724b860 glozow: ACK ffc674595cb19b2fdc5705b355bdd3e7f724b860, agree it's clearer for these comments to refer to the greppable name of the limit rather than the number Tree-SHA512: 462afc1c64543877ac58cb3acdb01d42c6d08abfb362802f29f3482d75401a2a8adadbc2facd222a9a9fefcaab6854865ea400f50ad60bec17831d29f7798afe
Diffstat (limited to 'src/kernel/mempool_limits.h')
0 files changed, 0 insertions, 0 deletions