gerryflap ,
@gerryflap@feddit.nl avatar

Awesome! Numpy has been such a useful tool during my data science study. Happy to see that they're not afraid to make some bigger changes.

wewbull ,

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 , (edited )

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.

pankuleczkapl ,
@pankuleczkapl@lemmy.dbzer0.com avatar

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

cbarrick ,

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.

rhymepurple ,

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?

cbarrick , (edited )

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.

rhymepurple ,

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.

wewbull ,

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.

sugar_in_your_tea ,

Honestly, I prefer C to C++ anyway. If they're going to switch to something, I'd prefer Rust.

But whatever, not my project, not my concern.

Alteon ,

We'll that's huge. NumPy is fantastic. Had to use it for a bunch of linear algebra calculations for a Mars Atmospheric Descent Calculator. Fully mapped the trajectory and flight path as it entered the Martian Atmosphere. Was a cool little program...

dinckelman ,

I’ve had a short period, where i had to use it during uni, and it was honestly a pretty solid experience. Unfortunately i can’t say that about MATLAB, as that was a nightmare in every way imaginable

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • kbinchat
  • All magazines
    •