You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There're examples that don't follow the suggestions outlined in the guidelines themselves, specifically NL.16 but potentially other as well, which makes it awkward when pointing people to read a particular rule — they read an example and start following the [wrong?] style without reading through all the guidelines — since nobody likes to read that much text, and NL is at the very end. It's aggravated by the fact that there's currently no check (that I know of) implemented for NL.16 specifically in static analysis tools like clang-format/clang-tidy.
The text was updated successfully, but these errors were encountered:
There're examples that don't follow the suggestions outlined in the guidelines themselves, specifically NL.16 but potentially other as well, which makes it awkward when pointing people to read a particular rule — they read an example and start following the [wrong?] style without reading through all the guidelines — since nobody likes to read that much text, and NL is at the very end. It's aggravated by the fact that there's currently no check (that I know of) implemented for NL.16 specifically in static analysis tools like clang-format/clang-tidy.
The text was updated successfully, but these errors were encountered: