NumPy 2.0.0 Release Notes
NumPy 2.0.0 is the first major release since 2006. It is the result of
11 months of development since the last feature release and is the work
of 212 contributors spread o...
Do you think a style guide is enough for an open source code base? Contributions could be coming from lots of directions, and the code review process to enforce a style guide is going to be a lot of work. Even rejecting something takes time.
Yup, we do it for Python and Javascript at work, and I do it on my Rust projects (and my older C projects). I don’t see why C++ should be any more difficult.
With a good style/best-practice guide, C++ can be quite productive of a language to work with.
Those kinds of guides typically define which standard/convention to use and which features not to use (cough exceptions cough).
I highly recommend Google’s C++ style guide: https://google.github.io/styleguide/cppguide.html.
You accidentally added a dot at the end of the link. Here’s the fixed one https://google.github.io/styleguide/cppguide.html
I intentionally added a period because it was the end of a sentence.
If your Lemmy app messed it up, then that’s a bug in its markdown parser.
Do you think a style guide is enough for an open source code base? Contributions could be coming from lots of directions, and the code review process to enforce a style guide is going to be a lot of work. Even rejecting something takes time.
This kind of thing can be easily automated nowadays. It’s not really a problem.
Yup, we do it for Python and Javascript at work, and I do it on my Rust projects (and my older C projects). I don’t see why C++ should be any more difficult.