-
Notifications
You must be signed in to change notification settings - Fork 37.7k
refactor: Use std::span over Span #29119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. Code Coverage & BenchmarksFor details see: https://corecheck.dev/bitcoin/bitcoin/pulls/29119. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. ConflictsNo conflicts as of last run. |
#include <type_traits> | ||
#include <span> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
double include
1745cf8
to
99364d7
Compare
99364d7
to
0bb7722
Compare
2936a4a
to
d62c3a4
Compare
449a307
to
b7d9f25
Compare
b7d9f25
to
b80b8ec
Compare
Concept ACK, provided we're migrating to |
9bd1162
to
9b56f63
Compare
Next step would be bitcoin-core/leveldb-subtree#45 |
9b56f63
to
6067754
Compare
d9eb61d
to
1377dd0
Compare
1377dd0
to
6e1b4b1
Compare
Now that it was show that it is possible to compile all code with |
std::span
allows static extents, which is a nice benefit over justSpan
.However, the interface of the two isn't identical and requires some more changes than just defining an alias. This is my current draft to compile with
std::span
. This should be the minimal changes required to get a green CI, but the changes may not be ideal, so this remains a draft.Also, this requires and is based on #29071.
In the meantime, changes that make sense on their own, can be split up.