Code formatting for C++

[jpivarski]

What code clang-format and clang-lint settings have been tried for formatting and linting C++ code in the Awkward Array codebase, particularly awkward-cpp?

[jpivarski]

This question's response is another victim of issue #8. Here's the raw log file:

2024-03-15T15:38:52.6715339Z INFO:answer-query:Loading database
2024-03-15T15:38:53.2750623Z INFO:answer-query:Waiting for query
2024-03-15T15:38:53.2753028Z INFO:answer-query:Query is 'What code clang-format and clang-lint settings have been tried for formatting and linting C++ code in the Awkward Array codebase, particularly awkward-cpp?\n'
2024-03-15T15:38:53.3271524Z INFO:answer-query:Getting 5 documents by direct similarity test
2024-03-15T15:38:54.2728673Z INFO:answer-query:Getting as many as 15 more by letting the LLM vary the query
2024-03-15T15:38:56.3019208Z INFO:langchain.retrievers.multi_query:Generated queries: ['1. Can you provide examples of code clang-format and clang-lint settings that have been tested for formatting and linting C++ code in the Awkward Array codebase, specifically awkward-cpp?', '2. What are some of the different configurations of code clang-format and clang-lint that have been experimented with for formatting and linting C++ code in the Awkward Array codebase, especially awkward-cpp?', '3. Which specific combinations of code clang-format and clang-lint settings have been explored for formatting and linting C++ code in the Awkward Array codebase, particularly in the context of awkward-cpp?']
2024-03-15T15:38:56.6910311Z INFO:answer-query:Found a total of 11 unique documents
2024-03-15T15:38:56.6919627Z INFO:answer-query:Which correspond to 11 raw documents
2024-03-15T15:38:56.6920761Z INFO:answer-query:Asking an LLM to rank the documents by usefulness
2024-03-15T15:38:58.9374017Z INFO:answer-query:LLM response: Score: 85 out of 100
2024-03-15T15:38:58.9374669Z 
2024-03-15T15:38:58.9378348Z The conversation mentions formatting and linting C++ code in the Awkward Array codebase, specifically awkward-cpp. While it doesn't provide specific clang-format and clang-lint settings, it indicates that these tools have been tried in the codebase. You can look for any specific examples of clang-format or clang-lint configurations that have been used in the codebase to help with your own formatting and linting needs.
2024-03-15T15:39:01.1694278Z INFO:answer-query:LLM response: Score: 60 out of 100
2024-03-15T15:39:01.1694946Z 
2024-03-15T15:39:01.1698942Z The conversation mentions the Awkward Array codebase, particularly awkward-cpp, which indicates that it may contain information about the code formatting and linting settings used in the project. Look for specific examples of clang-format and clang-lint settings that have been tried in the codebase. While it doesn't directly address your question, it provides a starting point for understanding the formatting and linting practices in the Awkward Array project.
2024-03-15T15:39:03.9612596Z INFO:answer-query:LLM response: Score: 80 out of 100
2024-03-15T15:39:03.9613315Z 
2024-03-15T15:39:03.9615907Z The conversation provides information on how to determine if `std::optional` is available in the ROOT environment, which can be useful for understanding the C++17 support. Look for the part where the availability of `std::optional` in PyROOT is checked using `hasattr(ROOT.std, "optional")`. Additionally, information on enforcing C++17 support in ROOT is discussed, which can be helpful for setting up the environment.
2024-03-15T15:39:05.6050706Z INFO:answer-query:LLM response: Score: 10 out of 100
2024-03-15T15:39:05.6051419Z 
2024-03-15T15:39:05.6055126Z The conversation does not address the specific clang-format and clang-lint settings used for formatting and linting C++ code in the Awkward Array codebase. However, it does provide insight into an error encountered while using Awkward Array, which could indirectly help in understanding the codebase better. Look for examples related to the error traceback and how different components of Awkward Array interact with each other.
2024-03-15T15:39:07.9085764Z INFO:answer-query:LLM response: Score: 45 out of 100
2024-03-15T15:39:07.9086345Z 
2024-03-15T15:39:07.9088602Z The conversation does not directly address the specific clang-format and clang-lint settings used in the Awkward Array codebase. However, it provides insight into the error handling and type recognition in Awkward Array, which can be helpful in understanding the codebase structure. Look for examples of error handling and type recognition to gain a better understanding of the codebase, which may indirectly lead to information about formatting and linting settings.
2024-03-15T15:39:09.8849021Z INFO:answer-query:LLM response: Score: 70 out of 100
2024-03-15T15:39:09.8849505Z 
2024-03-15T15:39:09.8852353Z The conversation provides information about using Doxygen for C++ documentation in the Awkward Array codebase. While it doesn't directly address clang-format and clang-lint settings, it does mention tools like Doxygen and Sphinx for documentation, which could be indicative of the development practices in the project. Look for references to Doxygen and C++ documentation tools in the conversation to gather insights into the project's code formatting and linting practices.
2024-03-15T15:39:11.5910889Z INFO:answer-query:LLM response: Score: 10 out of 100
2024-03-15T15:39:11.5911321Z 
2024-03-15T15:39:11.5914075Z The conversation does not directly address the question about clang-format and clang-lint settings for formatting and linting C++ code in the Awkward Array codebase. However, it does provide information about the minimal pyarrow version required in the codebase, which may indirectly help in understanding the version constraints for external libraries. Look for mentions of version requirements and constraints in the conversation to gather insights for setting up clang-format and clang-lint settings.
2024-03-15T15:39:13.4780278Z INFO:answer-query:LLM response: Score: 15 out of 100
2024-03-15T15:39:13.4780965Z 
2024-03-15T15:39:13.4784767Z While the conversation does not directly address the specific code formatting and linting settings for C++ code in the Awkward Array codebase, it does provide insight into the handling of ufuncs and typetracers in the codebase. You can look for examples of implementing ufuncs and typetracers in the conversation to understand the approach used for handling operations in Awkward Array, which might indirectly help you understand how code formatting and linting settings are managed.
2024-03-15T15:39:16.2361493Z INFO:answer-query:LLM response: Score: 60 out of 100
2024-03-15T15:39:16.2362143Z 
2024-03-15T15:39:16.2367542Z The conversation discusses the organization of C++ code in the Awkward Array codebase, particularly the idea of splitting the C++ code into a separate package called `awkward-core`. While it doesn't directly address clang-format and clang-lint settings, it provides insights into the structure and management of C++ code, which could indirectly impact the code formatting and linting practices. Look for mentions of the C++ code organization, splitting packages, and considerations for managing C++ code separately to gather insights that may inform your decision on clang-format and clang-lint settings.
2024-03-15T15:39:18.3342516Z INFO:answer-query:LLM response: Score: 20 out of 100
2024-03-15T15:39:18.3343205Z 
2024-03-15T15:39:18.3347087Z The conversation does not directly address the question about clang-format and clang-lint settings for C++ code. However, it does provide insights into handling and converting different types of arrays in Python and Numba, which could be useful for understanding data transformations. Look for mentions of Numba, NumPy arrays, and array transformations in the conversation to gain insights into handling C++ code formatting and linting.
2024-03-15T15:39:20.1885004Z INFO:answer-query:LLM response: Score: 10 out of 100
2024-03-15T15:39:20.1885852Z 
2024-03-15T15:39:20.1891340Z The conversation does not directly address the question about clang-format and clang-lint settings for C++ code in the Awkward Array codebase. However, it does provide information on tutorials and presentations related to analysis using Awkward Arrays, which could potentially lead you to resources where such settings might be discussed. Look for mentions of tutorials and presentations by the developers that may contain relevant information on coding practices and tools.
2024-03-15T15:39:20.1895531Z INFO:answer-query:Tokens Used: 37500
2024-03-15T15:39:20.1896026Z 	Prompt Tokens: 36301
2024-03-15T15:39:20.1896421Z 	Completion Tokens: 1199
2024-03-15T15:39:20.1896820Z Successful Requests: 12
2024-03-15T15:39:20.1897200Z Total Cost (USD): $0.0568495

and

2024-03-15T15:39:21.2641859Z {
2024-03-15T15:39:21.2666300Z     "query": "mutation AddDiscussionComment {\n                  addDiscussionComment(input: {\n                    discussionId: \"D_kwDOLaZ88c4AYVS5\",\n                    body: \"### Potentially useful sources\n\n**13 December, 2022:** GitHub issue [scikit-hep/awkward#1988](https://github.com/scikit-hep/awkward/issues/1988), Remove unused `num` kernels\n\nScore: 85 out of 100\n\nThe conversation mentions formatting and linting C++ code in the Awkward Array codebase, specifically awkward-cpp. While it doesn't provide specific clang-format and clang-lint settings, it indicates that these tools have been tried in the codebase. You can look for any specific examples of clang-format or clang-lint configurations that have been used in the codebase to help with your own formatting and linting needs.\n\n**23 March, 2022:** GitHub issue [scikit-hep/awkward#1382](https://github.com/scikit-hep/awkward/issues/1382), Test failure with 1.8.0 (1300-awkward-to-cpp-converter-with-cling)\n\nScore: 80 out of 100\n\nThe conversation provides information on how to determine if `std::optional` is available in the ROOT environment, which can be useful for understanding the C++17 support. Look for the part where the availability of `std::optional` in PyROOT is checked using `hasattr(ROOT.std, \"optional\")`. Additionally, information on enforcing C++17 support in ROOT is discussed, which can be helpful for setting up the environment.\n\n**2 April, 2020:** GitHub issue [scikit-hep/awkward#158](https://github.com/scikit-hep/awkward/issues/158), Strategy for documentation\n\nScore: 70 out of 100\n\nThe conversation provides information about using Doxygen for C++ documentation in the Awkward Array codebase. While it doesn't directly address clang-format and clang-lint settings, it does mention tools like Doxygen and Sphinx for documentation, which could be indicative of the development practices in the project. Look for references to Doxygen and C++ documentation tools in the conversation to gather insights into the project's code formatting and linting practices.\n\n**4 October, 2022:** GitHub issue [scikit-hep/awkward#1767](https://github.com/scikit-hep/awkward/issues/1767), Pickling of `Array`s should use `Form`'s dict representation\n\nScore: 60 out of 100\n\nThe conversation mentions the Awkward Array codebase, particularly awkward-cpp, which indicates that it may contain information about the code formatting and linting settings used in the project. Look for specific examples of clang-format and clang-lint settings that have been tried in the codebase. While it doesn't directly address your question, it provides a starting point for understanding the formatting and linting practices in the Awkward Array project.\n\n**15 February, 2023:** GitHub issue [scikit-hep/awkward#503](https://github.com/scikit-hep/awkward/issues/503), Move libawkward.so (etc) into its own package\n\nScore: 60 out of 100\n\nThe conversation discusses the organization of C++ code in the Awkward Array codebase, particularly the idea of splitting the C++ code into a separate package called `awkward-core`. While it doesn't directly address clang-format and clang-lint settings, it provides insights into the structure and management of C++ code, which could indirectly impact the code formatting and linting practices. Look for mentions of the C++ code organization, splitting packages, and considerations for managing C++ code separately to gather insights that may inform your decision on clang-format and clang-lint settings.\n\n**15 December, 2022:** GitHub issue [scikit-hep/awkward#2008](https://github.com/scikit-hep/awkward/issues/2008), `ak.type` does not accept \"anything `ak.to_layout` recognizes\"\n\nScore: 45 out of 100\n\nThe conversation does not directly address the specific clang-format and clang-lint settings used in the Awkward Array codebase. However, it provides insight into the error handling and type recognition in Awkward Array, which can be helpful in understanding the codebase structure. Look for examples of error handling and type recognition to gain a better understanding of the codebase, which may indirectly lead to information about formatting and linting settings.\n\"\n                  }) {\n                    comment {\n                      id\n                    }\n                  }\n                }"
2024-03-15T15:39:21.2685889Z }
2024-03-15T15:39:21.2686222Z response.status_code = 200
2024-03-15T15:39:21.2692177Z response.headers = {'Server': 'GitHub.com', 'Date': 'Fri, 15 Mar 2024 15:39:21 GMT', 'Content-Type': 'application/json; charset=utf-8', 'Transfer-Encoding': 'chunked', 'X-GitHub-Media-Type': 'github.v4; format=json', 'X-RateLimit-Limit': '5000', 'X-RateLimit-Remaining': '5000', 'X-RateLimit-Reset': '1710520761', 'X-RateLimit-Used': '0', 'X-RateLimit-Resource': 'graphql', 'Access-Control-Expose-Headers': 'ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset', 'Access-Control-Allow-Origin': '*', 'Strict-Transport-Security': 'max-age=31536000; includeSubdomains; preload', 'X-Frame-Options': 'deny', 'X-Content-Type-Options': 'nosniff', 'X-XSS-Protection': '0', 'Referrer-Policy': 'origin-when-cross-origin, strict-origin-when-cross-origin', 'Content-Security-Policy': "default-src 'none'", 'Vary': 'Accept-Encoding, Accept, X-Requested-With', 'Content-Encoding': 'gzip', 'X-GitHub-Request-Id': '9C41:2B31F2:363D20D:64CE61B:65F46BA9'}
2024-03-15T15:39:21.2709497Z {"errors":[{"message":"Parse error on \")`. Additionally, information on enforcing C++17 support in ROOT is discussed, which can be helpful for setting up the environment.\\n\\n**2 April, 2020:** GitHub issue [scikit-hep/awkward#158](https://github.com/scikit-hep/awkward/issues/158), Strategy for documentation\\n\\nScore: 70 out of 100\\n\\nThe conversation provides information about using Doxygen for C++ documentation in the Awkward Array codebase. While it doesn't directly address clang-format and clang-lint settings, it does mention tools like Doxygen and Sphinx for documentation, which could be indicative of the development practices in the project. Look for references to Doxygen and C++ documentation tools in the conversation to gather insights into the project's code formatting and linting practices.\\n\\n**4 October, 2022:** GitHub issue [scikit-hep/awkward#1767](https://github.com/scikit-hep/awkward/issues/1767), Pickling of `Array`s should use `Form`'s dict representation\\n\\nScore: 60 out of 100\\n\\nThe conversation mentions the Awkward Array codebase, particularly awkward-cpp, which indicates that it may contain information about the code formatting and linting settings used in the project. Look for specific examples of clang-format and clang-lint settings that have been tried in the codebase. While it doesn't directly address your question, it provides a starting point for understanding the formatting and linting practices in the Awkward Array project.\\n\\n**15 February, 2023:** GitHub issue [scikit-hep/awkward#503](https://github.com/scikit-hep/awkward/issues/503), Move libawkward.so (etc) into its own package\\n\\nScore: 60 out of 100\\n\\nThe conversation discusses the organization of C++ code in the Awkward Array codebase, particularly the idea of splitting the C++ code into a separate package called `awkward-core`. While it doesn't directly address clang-format and clang-lint settings, it provides insights into the structure and management of C++ code, which could indirectly impact the code formatting and linting practices. Look for mentions of the C++ code organization, splitting packages, and considerations for managing C++ code separately to gather insights that may inform your decision on clang-format and clang-lint settings.\\n\\n**15 December, 2022:** GitHub issue [scikit-hep/awkward#2008](https://github.com/scikit-hep/awkward/issues/2008), `ak.type` does not accept \" (STRING) at [4, 1136]","locations":[{"line":4,"column":1136}]}]}

The reason I asked this question is because I need this information to answer a comment, and it's a hard thing to search—the second time I have a real use for this functionality.

[jpivarski]

Here's a formatted version of what was supposed to be posted:

Potentially useful sources

13 December, 2022: GitHub issue scikit-hep/awkward#1988, Remove unused num kernels

Score: 85 out of 100

The conversation mentions formatting and linting C++ code in the Awkward Array codebase, specifically awkward-cpp. While it doesn't provide specific clang-format and clang-lint settings, it indicates that these tools have been tried in the codebase. You can look for any specific examples of clang-format or clang-lint configurations that have been used in the codebase to help with your own formatting and linting needs.

23 March, 2022: GitHub issue scikit-hep/awkward#1382, Test failure with 1.8.0 (1300-awkward-to-cpp-converter-with-cling)

Score: 80 out of 100

The conversation provides information on how to determine if std::optional is available in the ROOT environment, which can be useful for understanding the C++17 support. Look for the part where the availability of std::optional in PyROOT is checked using hasattr(ROOT.std, "optional"). Additionally, information on enforcing C++17 support in ROOT is discussed, which can be helpful for setting up the environment.

2 April, 2020: GitHub issue scikit-hep/awkward#158, Strategy for documentation

Score: 70 out of 100

The conversation provides information about using Doxygen for C++ documentation in the Awkward Array codebase. While it doesn't directly address clang-format and clang-lint settings, it does mention tools like Doxygen and Sphinx for documentation, which could be indicative of the development practices in the project. Look for references to Doxygen and C++ documentation tools in the conversation to gather insights into the project's code formatting and linting practices.

4 October, 2022: GitHub issue scikit-hep/awkward#1767, Pickling of Arrays should use Form's dict representation

Score: 60 out of 100

The conversation mentions the Awkward Array codebase, particularly awkward-cpp, which indicates that it may contain information about the code formatting and linting settings used in the project. Look for specific examples of clang-format and clang-lint settings that have been tried in the codebase. While it doesn't directly address your question, it provides a starting point for understanding the formatting and linting practices in the Awkward Array project.

15 February, 2023: GitHub issue scikit-hep/awkward#503, Move libawkward.so (etc) into its own package

Score: 60 out of 100

The conversation discusses the organization of C++ code in the Awkward Array codebase, particularly the idea of splitting the C++ code into a separate package called awkward-core. While it doesn't directly address clang-format and clang-lint settings, it provides insights into the structure and management of C++ code, which could indirectly impact the code formatting and linting practices. Look for mentions of the C++ code organization, splitting packages, and considerations for managing C++ code separately to gather insights that may inform your decision on clang-format and clang-lint settings.

15 December, 2022: GitHub issue scikit-hep/awkward#2008, ak.type does not accept "anything ak.to_layout recognizes"

Score: 45 out of 100

The conversation does not directly address the specific clang-format and clang-lint settings used in the Awkward Array codebase. However, it provides insight into the error handling and type recognition in Awkward Array, which can be helpful in understanding the codebase structure. Look for examples of error handling and type recognition to gain a better understanding of the codebase, which may indirectly lead to information about formatting and linting settings.

[jpivarski]

Actually, none of these are useful. I was looking for some three or four issues or PRs that were attempts to apply clang-format or clang-lint.

Oh! I excluded PRs from the index! Maybe none of them were issues and all of them were PRs.