Hacker Newsnew | past | comments | ask | show | jobs | submit | crest's commentslogin

How is this code portable to other platforms if it assumes that clang implies macOS?

This exactly the missing laptop/lowend desktop performance bracket missing in the ARM ecosystem. Make a Mini-ITX compatible board for the SoC, upstream drivers into mainline Linux (and *BSD), and people will buy it as the low power 24/7 board for the home. Is it so fucking hard not shoot yourself in both feet?

So you're better of using a 8x8->16 widening multiplication SIMD instruction or even just a multi register TBL/TBX instruction?

I guess that means they are fine with users ignoring their rights too? Just crack their software until something better comes along?

This should be treated as an organised crime syndicate stealing the purchase price from every customer.

Bend over for big tech!

About half of them read as "I tried to use C++ as a worse C" e.g. using struct initilisation instead of constructors, using malloc instead of new or new[].

My pet peeve with C++ is that the sequence point operator can be overloaded at which point it stops being a sequence point.


As the title indicate, this article is comparing construct-to-construct, not idiomatic code to idiomatic code. You probably won't use struct initialization in C++, yet the feature still exist, so it may be useful to someone to compare it to the similar feature in C.

What's the "sequence point operator"?


That's the comma operator. I didn't know you could overload it! That's pretty crazy. However, I have never seen anyone do that. Do you have any real world examples?

See e.g. the very-popular Eigen library, in which the type CommaInitializer basically exists for the sole purpose of overloading `operator,`, allowing a cleaner matrix initialization syntax.

https://gitlab.com/libeigen/eigen/blob/master/Eigen/src/Core...


Thanks!

If you want to know how bad it take your time with GCC 4.x before they responded to clang. GCC error messages used to be horrible for anything but the most trival errors. A single C++ template error could span multiple screens and still not tell you the location.


That's exactly what SEV is supposed to protect against. If you trust the hypervisor you don't have to encrypt your virtual machine's main memory.


Meanwhile those without cheap credit to burn through can't even get a reasonably sized system SSD without selling a kidney.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: