After formatting with clang, this looks ugly. I'd suggest using `private:` before first named section #16

Mr-S-Mirzoev · 2023-07-01T23:54:21Z

yaml-optimize/src/inc/optimizer/optimizer.h

Line 62 in ff84bfa

NAMED_PRIVATE_SECTION(Input data)

* Issue #7 | Fix state insolvency, add more debug code, add YO_ prefix to internal macros * Issue #7 | Try to fix the GitHub Action pipeline * Committing clang-format changes * Issue #7 | Trigger clang-format and fix logo and name * Issue #0 | General readability enhancements * Committing clang-format changes * Issue #17 | Add examples of library optimisation to README.md --------- Co-authored-by: Clang Robot <robot@example.com> Co-authored-by: GitHub Actions <actions@github.com>

Mr-S-Mirzoev added the enhancement New feature or request label Jul 1, 2023

Mr-S-Mirzoev mentioned this issue Jul 2, 2023

Issue #16 | Small enhancements #18

Merged

Mr-S-Mirzoev linked a pull request Jul 2, 2023 that will close this issue

Issue #16 | Small enhancements #18

Merged

Mr-S-Mirzoev closed this as completed in #18 Jul 3, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

After formatting with clang, this looks ugly. I'd suggest using `private:` before first named section #16

After formatting with clang, this looks ugly. I'd suggest using `private:` before first named section #16

Mr-S-Mirzoev commented Jul 1, 2023

After formatting with clang, this looks ugly. I'd suggest using private: before first named section #16

After formatting with clang, this looks ugly. I'd suggest using private: before first named section #16

Comments

Mr-S-Mirzoev commented Jul 1, 2023

After formatting with clang, this looks ugly. I'd suggest using `private:` before first named section #16

After formatting with clang, this looks ugly. I'd suggest using `private:` before first named section #16