125
NumPy 2.0.0 released (github.com)
submitted 2 years ago by to c/python@programming.dev
16 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 17 points 2 years ago (2 children)

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.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 16 points 2 years ago* (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 2 years ago (1 child)

    You accidentally added a dot at the end of the link. Here's the fixed one https://google.github.io/styleguide/cppguide.html

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 20 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    I'm curious about this. The source text of your comment appears that your comment was just the URL with no markdown. For your comment about a markdown parsing bug to be true, shouldn't the URL have been written in markdown with []() notation (or a space between the URL and the period) since a period is a valid URL character? For example, instead of typing https://google.github.io/styleguide/cppguide.html., should [https://google.github.io/styleguide/cppguide.html.](https://google.github.io/styleguide/cppguide.html) have been typed?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago* (last edited 2 years ago) (1 child)

    Huh. This got me curious.

    Yes, I did just type a bare URL. Every mature markdown parser I've used turns this into a link, and appropriately handles trailing punctuation.

    So I went to the spec, and it's explicitly called out that this is not an autolink. Autolinks must be explicitly surrounded with angle brackets <>.

    So yeah \shrug.

    https://spec.commonmark.org/0.31.2/#autolinks

    Edit to be clear: This means that both of our markdown parsers are wrong relative to the commonmark spec. But I'll argue that if a parser is going to attempt to autolink this, then handling trailing punctuation is better than not.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago

    I did not know about autolinks - thanks for the link!

    It is interesting how different parsers handle this exact situation. I usually am cautious about it because I typically am not sure how it will be handled if I am not explicit with the URL and additional text.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •