Tonight (CEST/Berlin): Meeting C++ Student Showcase
https://www.meetup.com/meeting-cpp-online/events/315410524/
https://redd.it/1uxwagq
@r_cpp
https://www.meetup.com/meeting-cpp-online/events/315410524/
https://redd.it/1uxwagq
@r_cpp
Meetup
Meeting C++ Student Showcase, Do., 16. Juli 2026, 19:00 | Meetup
The Meeting C++ Student Showcase:
Giving Students a spot where they can present their C++ projects as lightning talks. Meeting C++ organizes this together with a few C++ pr
Giving Students a spot where they can present their C++ projects as lightning talks. Meeting C++ organizes this together with a few C++ pr
A hardware-informed guide to Modern C++.
It explains how the source becomes instructions, how memory works, and why the machine cares about your choices.
If you're interested in systems programming, game engines, HFT, or writing fast software, give it a read.
read link
https://redd.it/1uyjnr5
@r_cpp
It explains how the source becomes instructions, how memory works, and why the machine cares about your choices.
If you're interested in systems programming, game engines, HFT, or writing fast software, give it a read.
read link
https://redd.it/1uyjnr5
@r_cpp
www.mubin.page
Builds a personalized, two-tone portfolio website with custom colors and a modern design.
The WG21 2026-07 post-Brno mailing is now available
The 2026-07 post-Brno WG21 mailing has been published. You can browse and search the full set of papers, organized by working group, at wg21.org:
https://wg21.org/mailing/2026-07/
Source mailing: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/#mailing2026-07
https://redd.it/1uyluxq
@r_cpp
The 2026-07 post-Brno WG21 mailing has been published. You can browse and search the full set of papers, organized by working group, at wg21.org:
https://wg21.org/mailing/2026-07/
Source mailing: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/#mailing2026-07
https://redd.it/1uyluxq
@r_cpp
WG21
July 2026 Mailing · WG21
Papers in the July 2026 WG21 mailing, with automated review notes.
The WG21 2026-07 post-Brno mailing is now available
The 2026-07 post-Brno WG21 mailing has been published. You can browse and search the full set of papers, organized by working group, at wg21.org:
https://wg21.org/mailing/2026-07/
Source mailing: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/#mailing2026-07
https://redd.it/1uykv7y
@r_cpp
The 2026-07 post-Brno WG21 mailing has been published. You can browse and search the full set of papers, organized by working group, at wg21.org:
https://wg21.org/mailing/2026-07/
Source mailing: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/#mailing2026-07
https://redd.it/1uykv7y
@r_cpp
WG21
July 2026 Mailing · WG21
Papers in the July 2026 WG21 mailing, with automated review notes.
Floating-Point Error Handling in C++: What Actually Works
https://johnnysswlab.com/floating-point-error-handling-in-c-what-actually-works/
https://redd.it/1uz0nv5
@r_cpp
https://johnnysswlab.com/floating-point-error-handling-in-c-what-actually-works/
https://redd.it/1uz0nv5
@r_cpp
Johnny's Software Lab
Floating-Point Error Handling in C++: What Actually Works - Johnny's Software Lab
Floating-point errors are unavoidable, but how you detect and handle them can make the difference between clean, high-performance C++ code and a debugging nightmare. In this article, we explore the practical techniques for handling NaNs, infinities, and other…
How I Stopped Designing Architecture and Started Writing a 3D Editor. Part 1
https://alexsyniakov.com/2026/07/11/programs-not-objects-how-i-stopped-designing-architecture-and-started-writing-a-3d-editor/
https://redd.it/1uz2ywa
@r_cpp
https://alexsyniakov.com/2026/07/11/programs-not-objects-how-i-stopped-designing-architecture-and-started-writing-a-3d-editor/
https://redd.it/1uz2ywa
@r_cpp
Alex on software development
Programs, Not Objects: How I Stopped Designing Architecture and Started Writing a 3D Editor
Today’s post is a bit different from my usual deep dives into mesh geometry. It’s a story about architecture – and about going back to the beginning. Think back to how you learned…
What do you think do I need continue learning cpp
Actually it's more about what would we need for cpp to be more popular
I personally think cpp is great language even thought I am getting bullied by compiler every single time or does my code classified as harassment/battery offence to compiler or only to human race whatever python backend doesn't know the greatness of real program language
Note: I started to learn cpp for unreal engine 5
and now unreal engine 6 will be ai slop with new useless "safe" language vers in this case does it looks similar to rust
Seriously zig rust possibly java okay even java knows it's bad it used for virtual machine versatility , ease of use
..
I am shiting you for universities and for Minecraft mods that's all
All of those languages tries to be better c or cpp but we still code in c and cpp
This why we need features to existing languages
From least controversial to most
0.1 delete lua I tried to make mods on it this NOT better python and I will not stand this lil timmi propaganda
1. Add saf++ library so idea is to make this library collection of safe analogies to unsafe instructions etc
2. Make "elegant" template errors readable without llm yes I have skill issue yes I am python dev at least I am not bibe coder I use ai to learn because I am not 10x guy I started learning python in 2020\~2021 so I am new to coding even newer to cpp 2026 I don't have reputation to vibe code I am not worthy of it and maybe you too
3 cpp needs debloat now because we can't focus on what important if we have to much to review we don't need 3 if I remember correctly copys of copys we don't need lua.. we don't need to have 5 different instructions to do one thing
One thing if you think I am wrong go programe python true I am bad at programing and I am new but two is important I will try to improve not only as a programer as a person and please if somebody didn't create compiler from cpp to lua I will do it myself on cpp
https://redd.it/1uz89ve
@r_cpp
Actually it's more about what would we need for cpp to be more popular
I personally think cpp is great language even thought I am getting bullied by compiler every single time or does my code classified as harassment/battery offence to compiler or only to human race whatever python backend doesn't know the greatness of real program language
Note: I started to learn cpp for unreal engine 5
and now unreal engine 6 will be ai slop with new useless "safe" language vers in this case does it looks similar to rust
Seriously zig rust possibly java okay even java knows it's bad it used for virtual machine versatility , ease of use
..
I am shiting you for universities and for Minecraft mods that's all
All of those languages tries to be better c or cpp but we still code in c and cpp
This why we need features to existing languages
From least controversial to most
0.1 delete lua I tried to make mods on it this NOT better python and I will not stand this lil timmi propaganda
1. Add saf++ library so idea is to make this library collection of safe analogies to unsafe instructions etc
2. Make "elegant" template errors readable without llm yes I have skill issue yes I am python dev at least I am not bibe coder I use ai to learn because I am not 10x guy I started learning python in 2020\~2021 so I am new to coding even newer to cpp 2026 I don't have reputation to vibe code I am not worthy of it and maybe you too
3 cpp needs debloat now because we can't focus on what important if we have to much to review we don't need 3 if I remember correctly copys of copys we don't need lua.. we don't need to have 5 different instructions to do one thing
One thing if you think I am wrong go programe python true I am bad at programing and I am new but two is important I will try to improve not only as a programer as a person and please if somebody didn't create compiler from cpp to lua I will do it myself on cpp
https://redd.it/1uz89ve
@r_cpp
Reddit
From the cpp community on Reddit
Explore this post and more from the cpp community
I really reconsider my life choices when I have to deal tooling bugs.
I like writing useful stuff, I'm tired of fighting tooling, I can legit say %80 percent of my time goes to dealing with dependencies build systems etc. Very rarely I have the privilege of actually writing stuff.
This shit sucks, like it really sucks. I hate it.
Is this normal, or only people who have it easy are web Devs and Java Devs since they are in a sandboxes environment and don't have deployment problems.
Am I crazy or is this common?
https://redd.it/1uzd6kw
@r_cpp
I like writing useful stuff, I'm tired of fighting tooling, I can legit say %80 percent of my time goes to dealing with dependencies build systems etc. Very rarely I have the privilege of actually writing stuff.
This shit sucks, like it really sucks. I hate it.
Is this normal, or only people who have it easy are web Devs and Java Devs since they are in a sandboxes environment and don't have deployment problems.
Am I crazy or is this common?
https://redd.it/1uzd6kw
@r_cpp
Reddit
From the cpp community on Reddit
Explore this post and more from the cpp community
Lifetime safety and invalidation without a borrow-checker: using type system analysis to get rid of many potentially invalidation cases WITHOUT annotations.
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4296r0.pdf
https://redd.it/1uzmxw9
@r_cpp
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4296r0.pdf
https://redd.it/1uzmxw9
@r_cpp
Clang and LLVM in Modern Gaming Platforms
https://youtu.be/1SM_wDUEEUg?is=8INW3jPuXJ_ONHlQ
https://redd.it/1uzp1so
@r_cpp
https://youtu.be/1SM_wDUEEUg?is=8INW3jPuXJ_ONHlQ
https://redd.it/1uzp1so
@r_cpp
YouTube
2026 EuroLLVM - Clang and LLVM in Modern Gaming Platforms
2026 EuroLLVM Developers' Meeting
https://llvm.org/devmtg/2026-04/
------
Title: Clang and LLVM in Modern Gaming Platforms
Speaker: Nicolai Haehnle, Tobias Hieta, Felix Klinge, Chris Bieneman, Jeremy Morse
------
Slides: https://llvm.org/devmtg/2026-04/…
https://llvm.org/devmtg/2026-04/
------
Title: Clang and LLVM in Modern Gaming Platforms
Speaker: Nicolai Haehnle, Tobias Hieta, Felix Klinge, Chris Bieneman, Jeremy Morse
------
Slides: https://llvm.org/devmtg/2026-04/…
A set of papers related to safety in July mailing list.
Since this is a topic that is interesting to many (including myself), I checked what the July mailing list has relevant to the safety topic and collected here what I found more relevant:
- A framework to systematically classify UB: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p3100r7.pdf
- core_ub: a run-time profile to guarantee lack of UB: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4317r0.pdf
- an initialization profile. This profile tries to give a guaranteed set of guaranteed initialization rules, banning impossible to analyze ones, statically: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4222r1.pdf
- deny by default + positive rules: a framework for invalidation detection with fewer annotations. This one is more of research than some of the other papers INHO right now, but looks interesting. Its main insight is that by adding deny by default combined with UB classification + as a default deny rule and a second layer of positive rules, combined with strict aliasing, annotations can be reduced to detect a subset of safety: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4296r0.pdf
- subsetting: banning unsafe constructs and usages through annotations to make the language safer by default. Collections of such rules could yield some specific profile or subset of profiles: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p3716r1.html
- on activating profiles proposes what the semantics of activating a profile should or should not be: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4314r0.html
- implicit contract assertions and profiles: this paper, among others, argues whether the base vehicle for implicit contract assertions should be a language feature or just a profile and explains that point of view in the matter: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4306r0.pdf
The papers related to pure contracts were intentionally left out since there are so many, but some are tangentially or directly related to the topic of safety.
Part of these papers lean on other foundational papers, such as yheprofiles framework (not from July mailing itself): https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p3589r2.pdf
I hope you enjoy it!
https://redd.it/1v0hynk
@r_cpp
Since this is a topic that is interesting to many (including myself), I checked what the July mailing list has relevant to the safety topic and collected here what I found more relevant:
- A framework to systematically classify UB: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p3100r7.pdf
- core_ub: a run-time profile to guarantee lack of UB: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4317r0.pdf
- an initialization profile. This profile tries to give a guaranteed set of guaranteed initialization rules, banning impossible to analyze ones, statically: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4222r1.pdf
- deny by default + positive rules: a framework for invalidation detection with fewer annotations. This one is more of research than some of the other papers INHO right now, but looks interesting. Its main insight is that by adding deny by default combined with UB classification + as a default deny rule and a second layer of positive rules, combined with strict aliasing, annotations can be reduced to detect a subset of safety: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4296r0.pdf
- subsetting: banning unsafe constructs and usages through annotations to make the language safer by default. Collections of such rules could yield some specific profile or subset of profiles: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p3716r1.html
- on activating profiles proposes what the semantics of activating a profile should or should not be: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4314r0.html
- implicit contract assertions and profiles: this paper, among others, argues whether the base vehicle for implicit contract assertions should be a language feature or just a profile and explains that point of view in the matter: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026/p4306r0.pdf
The papers related to pure contracts were intentionally left out since there are so many, but some are tangentially or directly related to the topic of safety.
Part of these papers lean on other foundational papers, such as yheprofiles framework (not from July mailing itself): https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p3589r2.pdf
I hope you enjoy it!
https://redd.it/1v0hynk
@r_cpp
Euro LLVM 2026: All talks related to C++ security
The recent Euro LLVM conference has several talks related to clang improvements that are either recent, in the process of eventually be pushed into upstream, or still in research status:
- Extending Lifetime Safety: Verification of [[clang::noescape] annotation](https://youtu.be/9Wcc7phM6kE?si=88ZZt6Gtj1zImMj)
- [Adding Nullability Checking and Annotations to Many Millions of Lines of Code](https://youtu.be/KzIRpQgRE0M?si=gZ1fnf7VHX5EeqNk)
- [Bounds Checking with the Clang Static Analyzer: Improvements and Insights](https://youtu.be/QisZYmCW9Rc?si=iUSuU5jSrnNaNQm)
- Finding Injection Vulnerabilities: Improvements of the Taint Analysis of the Clang static analyzer
- Capabilities Great and Small: CHERI, CHERIoT, and LLVM
All in all, a good overview of what clang can actually do today, with annotations as well, and what is being envisioned on the various security discussions.
https://redd.it/1v0ut9j
@r_cpp
The recent Euro LLVM conference has several talks related to clang improvements that are either recent, in the process of eventually be pushed into upstream, or still in research status:
- Extending Lifetime Safety: Verification of [[clang::noescape] annotation](https://youtu.be/9Wcc7phM6kE?si=88ZZt6Gtj1zImMj)
- [Adding Nullability Checking and Annotations to Many Millions of Lines of Code](https://youtu.be/KzIRpQgRE0M?si=gZ1fnf7VHX5EeqNk)
- [Bounds Checking with the Clang Static Analyzer: Improvements and Insights](https://youtu.be/QisZYmCW9Rc?si=iUSuU5jSrnNaNQm)
- Finding Injection Vulnerabilities: Improvements of the Taint Analysis of the Clang static analyzer
- Capabilities Great and Small: CHERI, CHERIoT, and LLVM
All in all, a good overview of what clang can actually do today, with annotations as well, and what is being envisioned on the various security discussions.
https://redd.it/1v0ut9j
@r_cpp
YouTube
2026 EuroLLVM - Extending Lifetime Safety: Verification of [[clang::noescape]] annotation
2026 EuroLLVM Developers' Meeting
https://llvm.org/devmtg/2026-04/
------
Title: Extending Lifetime Safety: Verification of [[clang::noescape]] annotation
Speaker: Abhinav Pradeep
------
Slides: https://llvm.org/devmtg/2026-04/slides/lightning_talk/ligh…
https://llvm.org/devmtg/2026-04/
------
Title: Extending Lifetime Safety: Verification of [[clang::noescape]] annotation
Speaker: Abhinav Pradeep
------
Slides: https://llvm.org/devmtg/2026-04/slides/lightning_talk/ligh…
I've invented labeled loop breaks
And now I don't believe it wasn't invented before, but I can't find any info on it. How long ago was it invented? Why isn't it used widely or even mentioned anywhere? What are the downsides?
Here's the main idea:
// Keyword - for, while, or do
// Tag - custom loop name
// ... - loop body
#define looptag(keyword, tag, ...)\
keyword(VAARGS)\
if(false)\
{\
tag##break: break;\
tag##continue: continue;\
}\
else\
/Here goes your loop body/
Here is the playground
https://redd.it/1v0s5da
@r_cpp
And now I don't believe it wasn't invented before, but I can't find any info on it. How long ago was it invented? Why isn't it used widely or even mentioned anywhere? What are the downsides?
Here's the main idea:
// Keyword - for, while, or do
// Tag - custom loop name
// ... - loop body
#define looptag(keyword, tag, ...)\
keyword(VAARGS)\
if(false)\
{\
tag##break: break;\
tag##continue: continue;\
}\
else\
/Here goes your loop body/
Here is the playground
https://redd.it/1v0s5da
@r_cpp
godbolt.org
Compiler Explorer - C++ (x86-64 clang (trunk))
#define loop_tag(keyword, tag, ...)\
keyword(__VA_ARGS__)\
if(false)\
{\
tag##_break: break;\
tag##_continue: continue;\
}\
else
#define for_tag(tag, ...)\
loop_tag(for, tag, __VA_ARGS__)
#define while_tag(tag…
keyword(__VA_ARGS__)\
if(false)\
{\
tag##_break: break;\
tag##_continue: continue;\
}\
else
#define for_tag(tag, ...)\
loop_tag(for, tag, __VA_ARGS__)
#define while_tag(tag…
Looking for ideas for the next version of my low-latency C++ project
**Planning the next version of my low-latency C++ project**
A few weeks ago I shared my C++20 low-latency trading project, **Pulse-Order**, GitHub: [https://github.com/Shivfun99/Pulse-Order](https://github.com/Shivfun99/Pulse-Order) and I was genuinely surprised by the response. Thanks to everyone who took the time to review the project, challenge my design decisions, and explain trade-offs from real low-latency systems. Those discussions helped me identify several areas where the project can be improved.
**Original post:**
[https://www.reddit.com/r/quantindia/s/u45s60B33Q](https://www.reddit.com/r/quantindia/s/u45s60B33Q)
[https://www.reddit.com/r/quant/s/IHKVkv0UGv](https://www.reddit.com/r/quant/s/IHKVkv0UGv)
The current version includes:
* Binary market data parsing
* L2 OB
* Risk checks
* DPDK packet processing
* Application-side latency benchmarking
I'm now starting work on the next version.
Some areas I'm considering are:
* Lock-free multi-core architecture
* Multi-symbol order books
* Real market data replay
* Hardware timestamping
* AF\_XDP vs DPDK
* Exchange gateway simulation
* Order lifecycle (new/modify/cancel/fills)
* Tail-latency analysis under burst traffic
For those who have worked on low-latency systems or exchange infrastructure, **which of these would you tackle first? Is there an important systems component that you think should be added before anything else?**
I'm mainly interested in improving the systems engineering aspects rather than the trading strategy itself.
https://redd.it/1v11g3n
@r_cpp
**Planning the next version of my low-latency C++ project**
A few weeks ago I shared my C++20 low-latency trading project, **Pulse-Order**, GitHub: [https://github.com/Shivfun99/Pulse-Order](https://github.com/Shivfun99/Pulse-Order) and I was genuinely surprised by the response. Thanks to everyone who took the time to review the project, challenge my design decisions, and explain trade-offs from real low-latency systems. Those discussions helped me identify several areas where the project can be improved.
**Original post:**
[https://www.reddit.com/r/quantindia/s/u45s60B33Q](https://www.reddit.com/r/quantindia/s/u45s60B33Q)
[https://www.reddit.com/r/quant/s/IHKVkv0UGv](https://www.reddit.com/r/quant/s/IHKVkv0UGv)
The current version includes:
* Binary market data parsing
* L2 OB
* Risk checks
* DPDK packet processing
* Application-side latency benchmarking
I'm now starting work on the next version.
Some areas I'm considering are:
* Lock-free multi-core architecture
* Multi-symbol order books
* Real market data replay
* Hardware timestamping
* AF\_XDP vs DPDK
* Exchange gateway simulation
* Order lifecycle (new/modify/cancel/fills)
* Tail-latency analysis under burst traffic
For those who have worked on low-latency systems or exchange infrastructure, **which of these would you tackle first? Is there an important systems component that you think should be added before anything else?**
I'm mainly interested in improving the systems engineering aspects rather than the trading strategy itself.
https://redd.it/1v11g3n
@r_cpp
GitHub
GitHub - Shivfun99/Pulse-Order
Contribute to Shivfun99/Pulse-Order development by creating an account on GitHub.