101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

487
active users

#cpp17

0 posts0 participants0 posts today

#GCC 14's <experimental/simd> will support ARM's SVE instruction set. Thanks to Srinivas Yadav Singanaboina for the contribution! Please take it for a good test drive and report issues so that the C++26 std::simd can become even better! #cpp #cpp17 #cpp26

There is a new #job opportunity at #OpenVPN for a #automation #QA role

careers.openvpn.net/o/core-aqa

We want to expand our Core team (developing the "lower level" components of the OpenVPN stack) to become even better at testing our low-level C++ code.

Currently we target #cpp17 and will move forward as compilers improve across all supported platforms.

Feel free to reach out if you have any questions!

OpenVPNCore AQA Engineer (C++)We are looking for a seasoned Automation QA with a keen eye for detail, a passion for testing, and an eagerness to contribute to our product. The Core team at OpenVPN Inc. is responsible for technolog

Okay, I need the #Fediverse swarm intelligence regarding #cplusplus:

Let's say I write a function like this, in C++17 or later:

```
inline int Calculate(int a, int b) {
return a+b;
}
```

I put it in a file called `calculate.h` and include (and use) it at multiple other places in the code.

Let's assume the function is not inlined at call sites. Due to the `inline` keyword, the compiler will ensure that `Calculate()` exists only once. (See en.cppreference.com/w/cpp/lang)

Question: Will the compiler generate the instructions multiple times, or does it avoid compiling a function body that's already going to be compiled in a different translation unit?

In other words: Do lots of `inline` functions in header files slow down compilation?

en.cppreference.cominline specifier - cppreference.com
#cpp17#cpp20#cpp