You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ffff4a2 bench: Update span-serialize comment (MarcoFalke)
fa4d6ec refactor: Avoid false-positive gcc warning (MarcoFalke)
fa94233 scripted-diff: Bump copyright headers after std::span changes (MarcoFalke)
fa0c6b7 refactor: Remove unused Span alias (MarcoFalke)
fade0b5 scripted-diff: Use std::span over Span (MarcoFalke)
fadccc2 refactor: Make Span an alias of std::span (MarcoFalke)
fa27e36 test: Fix broken span_tests (MarcoFalke)
fadf02e refactor: Return std::span from MakeUCharSpan (MarcoFalke)
fa720b9 refactor: Return std::span from MakeByteSpan (MarcoFalke)
Pull request description:
`Span` has some issues:
* It does not support fixed-size spans, which are available through `std::span`.
* It is confusing to have it available and in use at the same time with `std::span`.
* It does not obey the standard library iterator build hardening flags. See bitcoin/bitcoin#31272 for a discussion. For example, this allows to catch issues like the one fixed in commit fabeca3.
Both types are type-safe and can even implicitly convert into each other in most contexts.
However, exclusively using `std::span` seems less confusing, so do it here with a scripted-diff.
ACKs for top commit:
l0rinc:
reACK ffff4a2
theuni:
ACK ffff4a2.
Tree-SHA512: 9cc2f1f43551e2c07cc09f38b1f27d11e57e9e9bc0c6138c8fddd0cef54b91acd8b14711205ff949be874294a121910d0aceffe0e8914c4cff07f1e0e87ad5b8
0 commit comments