127

submitted 3 weeks ago by rwnobrega@lemmy.world to c/python@programming.dev

17 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] wewbull@feddit.uk 17 points 3 weeks ago

Furthermore there are many changes to NumPy internals, including continuing to migrate code from C to C++, that will make it easier to improve and maintain NumPy in the future.

I realise that C can be rather low level a lot of the time, but I'm not sure I'd pick C++ to help keep things easy to maintain. It opens up a Pandora's box of possibilities.

[-] cbarrick@lemmy.world 16 points 3 weeks ago* (last edited 3 weeks ago)

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.

[-] wewbull@feddit.uk 1 points 3 weeks ago

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.

[-] balder1993@programming.dev 5 points 3 weeks ago

This kind of thing can be easily automated nowadays. It’s not really a problem.

[-] sugar_in_your_tea@sh.itjust.works 2 points 3 weeks ago

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.