Introduce official clang-format by lpranam · Pull Request #596 · boostorg/gil
mloskot
changed the title
introduce official clang-format
Introduce official clang-format
mloskot added a commit to mloskot/gil that referenced this pull request
Apr 25, 2021- Trailing return types everywhere - Optionally, return type deduction where sensible (simple and short functions) This is related to introduction of common .clang-format, see boostorg#596 (comment)
mloskot added a commit to mloskot/gil that referenced this pull request
Apr 26, 2021- Trailing return types everywhere - Optionally, return type deduction where sensible (simple and short functions) This is related to introduction of common .clang-format, see boostorg#596 (comment)
mloskot added a commit to mloskot/gil that referenced this pull request
May 6, 2021- Trailing return types everywhere - Optionally, return type deduction where sensible (simple and short functions) This is related to introduction of common .clang-format, see boostorg#596 (comment)
mloskot added a commit to mloskot/gil that referenced this pull request
May 6, 2021- Trailing return types everywhere - Optionally, return type deduction where sensible (simple and short functions) This is related to introduction of common .clang-format, see boostorg#596 (comment)
This is intermediate commit to clearly show the .clang-format tweaks that I'd like to propose to @lpranam 's original.
harshitpant1 added a commit to harshitpant1/gil that referenced this pull request
Jun 23, 2021Uses the clang-format configuration provided in the latest commit of PR boostorg#596. Formatting is applied to test file and example file as well. I have made no changes whatsoever after using the clang-format.
mloskot added a commit that referenced this pull request
Jun 27, 2022- Trailing return types everywhere - Optionally, return type deduction where sensible (simple and short functions) This is related to introduction of common .clang-format, see #596 (comment)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters