primitives/transaction.h
locally in src/
.
primitives/transaction.h
locally in src/
.
All aboard the obvious-ACK train :).
utACK.
Nit: We expect to find primitives/transaction.h locally in src/.
utACK as it matches the common convention better.
Though sometimes I wonder whether this convention is a good idea. include <>
searches relative to the include paths, include ""
relative to the directory of the current source file, then the include paths. We know primitives/
is relative to the source root of the repository, so it doesn’t really need to look anywhere else. Especially not if it is already in primitives/
, e.g.
primitives/block.h
includes "primitives/transaction.h"
, then it makes it look in src/primitives/primitives
src/wallet/feebumper.h
includes "primitives/transaction.h"
, it makes it look in src/wallet/primitives
!So with regard to unambiguity, this is a change for the worse.
4@@ -5,7 +5,7 @@
5 #ifndef BITCOIN_WALLET_FEEBUMPER_H
6 #define BITCOIN_WALLET_FEEBUMPER_H
7
8-#include <primitives/transaction.h>
9+#include "primitives/transaction.h"
With quotes should be relative?
0#include "../primitives/transaction.h"
wallet/wallet.h
:-) Introduced in 97375727b8f3b7d26c7c813630a6139005b5c5c9.
#include <>
) instead on the longer run (https://github.com/bitcoin/bitcoin/pull/10976#issuecomment-322397113) and I think that’d be superior.