[trivial] Add end of namespace comments. Improve consistency.#9544
Conversation
2553d2b to
7140b87
Compare
|
Merge conflict resolved! |
src/base58.cpp
Outdated
There was a problem hiding this comment.
@jtimon My reasoning behind that was to achieve consistency how anonymous namespaces are indicated. Consistency in order to improve readability and allow for automatic identification of missing/incorrect end of namespace comments.
// namespace is the form preferred by the clang-tooling (clang-tidy, etc). // anonymous namespace is also quite common. I haven't seen // anon namespace before, but let me know if the choice of // anon namespace is intentional and I'll adjust this PR :-)
There was a problem hiding this comment.
Well, it just seems to me that the same consistency can be achieved leaving "anon namespace" for anonymous namespaces with less disruption. But if clang prefers // namespace or // anonymous namespace I don't have a strong opinion.
|
Any changes needed before merge? :-) |
|
The question should read: How can I attract you to the review? My answer is: sorry, I do not know. I'm pro |
|
@paveljanik I see! If the consensus opinion is that end of namespace marks are optional then this PR is redundant and I'll close it :-) |
|
I think the point is that if end-of-namespace comments are to be required, they should be mentioned in |
|
@practicalswift I do now know what the consensus is, but my opinion is the same as @laanwj 's. |
15bd40f to
602d1aa
Compare
|
@laanwj Good point! I've added a note to |
602d1aa to
11d4870
Compare
|
I'd slightly prefer |
|
@paveljanik It seems like
|
|
@practicalswift yes. But it seems like the author forget to add the real name of the namespace after it ;-) |
src/univalue/lib/univalue.cpp
Outdated
There was a problem hiding this comment.
This is univalue -> please report upstream.
|
Concept ACK. Please remove univalue change. Then utACK |
11d4870 to
8530606
Compare
|
@paveljanik Removed univalue change as requested :-) |
|
ACK 8530606 Thanks! |
|
@paveljanik Thanks for reviewing! Let me know if any further tweaks are needed :-) |
470a0ee to
c629d4f
Compare
c629d4f to
4c92401
Compare
|
Conflicts resolved! |
|
Fast re-review checked that still doesn't need testing ACK 486a5d7 |
doc/developer-notes.md
Outdated
There was a problem hiding this comment.
@jtimon Sorry I'm not sure I follow - where should the extra spaces be placed? :-)
There was a problem hiding this comment.
s/ ```/```/ ?
EDIT: not important
486a5d7 to
5a9b508
Compare
|
@jtimon Fixed! :-) |
|
utACK 5a9b508 |
…ency. 5a9b508 [trivial] Add end of namespace comments (practicalswift) Tree-SHA512: 92b0fcae4d1d3f4da9e97569ae84ef2d6e09625a5815cd0e5f0eb6dd2ecba9852fa85c184c5ae9de5117050330ce995e9867b451fa8cd5512169025990541a2b
…consistency. 5a9b508 [trivial] Add end of namespace comments (practicalswift) Tree-SHA512: 92b0fcae4d1d3f4da9e97569ae84ef2d6e09625a5815cd0e5f0eb6dd2ecba9852fa85c184c5ae9de5117050330ce995e9867b451fa8cd5512169025990541a2b
No description provided.