Use of angle brackets around file names for include statements about feather

[wesm]

No, unless there is some problem with using double quotes in header files associated with feather

https://google.github.io/styleguide/cppguide.html#Names_and_Order_of_Includes

[elfring]

I suggest to reconsider the consequences of the following wording from the section "16.2 Source file inclusion" in the standard specification for the programming language "C++".

…
The named source file is searched for in an implementation-defined manner. If this search is not supported, or if the search fails, the directive is reprocessed as if it read

#include <h-char-sequence> new-line
…

• How do you think about to avoid "a duplicated file search" here?
• Would you like to restrict the searched directories for header files of your software?

[wesm]

I'm afraid I still don't see the problem, or at least your argument is not clear. My understanding is that using double quotes for headers that are internal to a particular project is the best practice.

Also, I have just scanned through your other reported issues on GitHub, and I find your public behavior to be extremely trollish. I strongly encourage you to change the way you are interacting with open source projects and to engage in a way that is more helpful (by explaining problems clearly, rather than posting links to things to read, or writing patches). If you continue to do it here, I will report abuse with GitHub. Thank you