Renamed UniValue::__pushKV to UniValue::pushKVEnd. #27822

Any identifier starting with 2 _ is reserved for the compiler and thus must not be used.

See: https://stackoverflow.com/a/228797/7130273

<!--e57a25ab6845829454e8d69fc972939a-->

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

<!--021abf342d371248e50ceaed478a90ca-->

Reviews

See 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.

<!--174a7506f384e20aa4161008e828411d-->

Conflicts

Reviewers, this pull request conflicts with the following ones:

• #27788 (rpc: Be able to access RPC parameters by name by achow101)
• #27742 ([NO MERGE] BIP331 Ancestor Package Relay by glozow)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

See https://github.com/bitcoin/bitcoin/blob/master/doc/developer-notes.md#scripted-diffs for changes like this.

lgtm ACK acad989e67a57709dbb882c97852c2067f9dc65e

Does it make sense to force such changes with the Clang's -Wreserved-identifier diagnostic flag?

@Brotcrunsher are you going to rebase this?

Does it make sense to force such changes with the Clang's -Wreserved-identifier diagnostic flag?

I get a warning about _EraseTx and this:

diff --git a/src/support/allocators/secure.h b/src/support/allocators/secure.h
index a0918bf463..b2076bea07 100644
--- a/src/support/allocators/secure.h
+++ b/src/support/allocators/secure.h
@@ -32,9 +32,9 @@ struct secure_allocator : public std::allocator<T> {
     {
     }
     ~secure_allocator() noexcept {}
-    template <typename _Other>
+    template <typename Other>
     struct rebind {
-        typedef secure_allocator<_Other> other;
+        typedef secure_allocator<Other> other;
     };
 
     T* allocate(std::size_t n, const void* hint = nullptr)
diff --git a/src/support/allocators/zeroafterfree.h b/src/support/allocators/zeroafterfree.h
index 795eea3bc0..2dc644c242 100644
--- a/src/support/allocators/zeroafterfree.h
+++ b/src/support/allocators/zeroafterfree.h
@@ -27,9 +27,9 @@ struct zero_after_free_allocator : public std::allocator<T> {
     {
     }
     ~zero_after_free_allocator() noexcept {}
-    template <typename _Other>
+    template <typename Other>
     struct rebind {
-        typedef zero_after_free_allocator<_Other> other;
+        typedef zero_after_free_allocator<Other> other;
     };
 
     void deallocate(T* p, std::size_t n)

Does it make sense to force such changes with the Clang's -Wreserved-identifier diagnostic flag?

I get a warning about _EraseTx and this:

I got the same. Could be added to this PR, no?

Please follow the commit subject max len, according to https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#committing-patches

Please follow the commit subject max len

Thanks for the feedback, done! One detail question regarding the max length (not important for this Commit, just want to learn for the future). Are CI triggers like "scripted-diff: " considered as part of the subject line and thus part of the 80 chars limitation?

lgtm ACK bdea2bb1147bbd22f8b4fa406262470f9d084215

Does it make sense to force such changes with the Clang's -Wreserved-identifier diagnostic flag?

Doing so is going to require further suppressing, or changes in upstream code. i.e:

./minisketch/include/minisketch.h:2:9: warning: macro name is a reserved identifier [-Wreserved-macro-identifier]
#define _MINISKETCH_H_ 1
        ^
1 warning generated.
./crypto/ctaes/ctaes.h:8:9: warning: macro name is a reserved identifier [-Wreserved-macro-identifier]
#define _CTAES_H_ 1
        ^
1 warning generated.
./leveldb/port/thread_annotations.h:16:9: warning: macro name is a reserved identifier [-Wreserved-macro-identifier]
#define THREAD_ANNOTATION_ATTRIBUTE__(x) __attribute__((x))
        ^
1 warning generated.
minisketch/src/util.h:16:11: warning: macro name is a reserved identifier [-Wreserved-macro-identifier]
#  define __GNUC_PREREQ(_maj,_min) \
          ^
3 warnings generated.