#cpp23 — Public Fediverse posts

May I make you aware of the phantastic @compiler_explorer, that totally indispensable tool to every software developer - the brainchild of @mattgodbolt ?

I can speak only as an average C++ developer who works at a small company, and who happens to be stranded in the C++ committee.

For my own experiments, I have a personal bookmark in my browser called "C++23 playground" as a starting point for for more elaborate adventures in the C++ lands. May be, it helps you as well:

https://godbolt.org/z/Mz96j16nx

To the best of my knowledge, the provided flags will give you some highly recommended defaults for compiler diagnostics and maximum language conformance, in the three major implementations Clang/libc++, GCC/libstdc++, and MSVC/MS-STL. Maybe you'll get some inspiration for your daily grind.

Please support Matt and the entire CE team 🤘, f.e. by getting some swag that we nerds can proudly present in the public and wear as protective gear ☺️

Visit https://shop.compiler-explorer.com/promo/BLACKFRIDAY 🤩

#cpp #cpp23 #cplusCplus #programming

Are you using std::ranges in your C++ code? If not, what is stopping you?

Ranges introduced a huge paradigm shift in the way we can write our C++ code. They can make the code way shorter, way better separated, and what's best - way more resilient to both logical and memory-related bugs. 🐞

If you haven't yet dabbled in ranges yourself, I've prepared a kind of cheatsheet reference article exploring many everyday use cases and how they can be improved by using the std::ranges library. 📏

You can read the article for free on my Medium:
➤ https://medium.com/@nerudaj/you-need-to-start-using-c-s-ranges-cf80c9f38602

What are your experiences with this library? Tell me in the comments 👇

#cpp #softwareengineering #memorysafety #cpp23

Are you using std::ranges in your C++ code? If not, what is stopping you?

Ranges introduced a huge paradigm shift in the way we can write our C++ code. They can make the code way shorter, way better separated, and what's best - way more resilient to both logical and memory-related bugs. 🐞

If you haven't yet dabbled in ranges yourself, I've prepared a kind of cheatsheet reference article exploring many everyday use cases and how they can be improved by using the std::ranges library. 📏

You can read the article for free on my Medium:
➤ https://medium.com/@nerudaj/you-need-to-start-using-c-s-ranges-cf80c9f38602

What are your experiences with this library? Tell me in the comments 👇

#cpp #softwareengineering #memorysafety #cpp23

Are you using std::ranges in your C++ code? If not, what is stopping you?

Ranges introduced a huge paradigm shift in the way we can write our C++ code. They can make the code way shorter, way better separated, and what's best - way more resilient to both logical and memory-related bugs. 🐞

If you haven't yet dabbled in ranges yourself, I've prepared a kind of cheatsheet reference article exploring many everyday use cases and how they can be improved by using the std::ranges library. 📏

You can read the article for free on my Medium:
➤ https://medium.com/@nerudaj/you-need-to-start-using-c-s-ranges-cf80c9f38602

What are your experiences with this library? Tell me in the comments 👇

#cpp #softwareengineering #memorysafety #cpp23

Are you using std::ranges in your C++ code? If not, what is stopping you?

Ranges introduced a huge paradigm shift in the way we can write our C++ code. They can make the code way shorter, way better separated, and what's best - way more resilient to both logical and memory-related bugs. 🐞

If you haven't yet dabbled in ranges yourself, I've prepared a kind of cheatsheet reference article exploring many everyday use cases and how they can be improved by using the std::ranges library. 📏

You can read the article for free on my Medium:
➤ https://medium.com/@nerudaj/you-need-to-start-using-c-s-ranges-cf80c9f38602

What are your experiences with this library? Tell me in the comments 👇

#cpp #softwareengineering #memorysafety #cpp23

Are you using std::ranges in your C++ code? If not, what is stopping you?

Ranges introduced a huge paradigm shift in the way we can write our C++ code. They can make the code way shorter, way better separated, and what's best - way more resilient to both logical and memory-related bugs. 🐞

If you haven't yet dabbled in ranges yourself, I've prepared a kind of cheatsheet reference article exploring many everyday use cases and how they can be improved by using the std::ranges library. 📏

You can read the article for free on my Medium:
➤ https://medium.com/@nerudaj/you-need-to-start-using-c-s-ranges-cf80c9f38602

What are your experiences with this library? Tell me in the comments 👇

#cpp #softwareengineering #memorysafety #cpp23

Did I just hand-write an implementation of #cpp23 std::expected for use in #cpp11? Very, very yes.

Is it complete? No. But it is functional enough.

Am I pleased with it? Also very yes!

Will I use it in #ProjectSpecialK? I dunno, maybe. We'll see.

Stephan is busy, so I'm on my private "🐞 STL Bug Bash II" as he calls it.

With
* a simple fix in <chrono> 🥲
* a hacky 😦 workaround in <chrono>
* and a compatible (!) attachment in module 'std' of all the entities from the C++ standard library 🙄

I can mix #includes and import std from the modularized ms-stl 🎉🚀✨

Gradual adoption of a modularized #cpp20 or #cpp23 standard library is now possible as soon as said issues are fixed and publicly available!