-
Stay up-to-date with everything C++! Content directly fetched from the subreddit just for you. Join our group for discussions : @programminginc Powered by : @r_channels
Xmake v3.0.6 Released, Android Native Apps, Flang, AppImage/dmg Support
https://xmake.io/posts/xmake-update-v3.0.6.html
https://redd.it/1q3qjpu
@r_cpp
A reference wrapper to replace raw pointers in my project
https://gist.github.com/ShirenY/4ce18484b45e2554e2a57470fff121bf
I'm pretty sure someone has done this before, but I couldn't find anything like it online. Would it be worth replacing the raw pointers in my project with this?
https://redd.it/1q3kydg
@r_cpp
SIMD with more than one argument, multiple translation units, ABI
https://pseyfert.codeberg.page/2025/12/simd-with-more-than-one-argument/
https://redd.it/1q2adhg
@r_cpp
audio-driven logic
auto source_sine = vega.Sine(0.2, 1.0f); // 0.2 Hz slow oscillator
static double last_input = 0.0;
auto logic = vega.Logic([](double input) {
// Arhythmic: true when sine crosses zero AND going positive
bool crossed_zero = (last_input < 0.0) && (input >= 0.0);
last_input = input;
return crossed_zero;
});
source_sine >> logic;
// 3. When logic fires, excite the bell
logic->on_change_to(true, [bell](auto& ctx) {
bell->excite(get_uniform_random(0.5f, 0.9f));
bell->set_fundamental(get_uniform_random(220.0f, 1000.0f));
});
// 4. Graphics (same as before)
auto window = MayaFlux::create_window({ "Audio-Driven Bell", 1280, 720 });
auto points = vega.PointCollectionNode(500) | Graphics;
auto geom = vega.GeometryBuffer(points) | Graphics;
geom->setup_rendering({ .target_window = window });
window->show();
// 5. Visualize: points grow when bell strikes (when logic fires)
MayaFlux::schedule_metro(0.016, [points]() {
static float angle = 0.0f;
static float radius = 0.0f;
if (last_input != 0) {
angle += 0.5f; // Quick burst on strike
radius += 0.002f;
} else {
angle += 0.01f; // Slow growth otherwise
radius += 0.0001f;
}
if (radius > 1.0f) {
radius = 0.0f;
points->clear_points();
}
float x = std::cos(angle) * radius;
float y = std::sin(angle) * radius * (16.0f / 9.0f);
float brightness = 1.0f - (radius * 0.7f);
points->add_point(Nodes::GpuSync::PointVertex {
.position = glm::vec3(x, y, 0.0f),
.color = glm::vec3(brightness, brightness * 0.8f, 1.0f),
.size = 8.0f + radius * 4.0f });
});
}
```
https://redd.it/1q1uuok
@r_cpp
Swapping two blocks of memory that reside inside a larger block, in constant memory
https://devblogs.microsoft.com/oldnewthing/20260101-00/?p=111955
https://redd.it/1q1r6wv
@r_cpp
Every LLM hallucinates that std::vector deletes elements in a LIFO order
https://am17an.bearblog.dev/every-llm-hallucinates-stdvector-deletes-elements-in-a-lifo-order
https://redd.it/1q1syp2
@r_cpp
C++20 Features Explained: Modules, Concepts, Ranges, and Coroutines
https://youtu.be/H9laXhzkKVM
https://redd.it/1q2qcfl
@r_cpp
C++ Jobs - Q1 2026
Rules For Individuals
---------------------
* **Don't** create top-level comments - those are for employers.
* Feel free to reply to top-level comments with **on-topic** questions.
* I will create top-level comments for **meta** discussion and **individuals looking for work**.
Rules For Employers
-------------------
* If you're hiring **directly**, you're fine, skip this bullet point. If you're a **third-party recruiter**, see the extra rules below.
* **Multiple** top-level comments per employer are now permitted.
+ It's still fine to consolidate multiple job openings into a single comment, or mention them in replies to your own top-level comment.
* **Don't** use URL shorteners.
+ [reddiquette][] forbids them because they're opaque to the spam filter.
* **Use** the following template.
+ Use \*\*two stars\*\* to **bold text**. Use empty lines to separate sections.
* **Proofread** your comment after posting it, and edit any formatting mistakes.
Template
--------
\*\*Company:\*\* [Company name; also, use the "formatting help" to make it a link to your company's website, or a specific careers page if you have one.]
\*\*Type:\*\* [Full time, part time, internship, contract, etc.]
\*\*Compensation:\*\* [This section is **optional**, and you can omit it without explaining why. However, including it will help your job posting stand out as there is extreme demand from candidates looking for this info. If you choose to provide this section, it must contain (a range of) **actual numbers** - don't waste anyone's time by saying "Compensation: Competitive."]
\*\*Location:\*\* [Where's your office - or if you're hiring at multiple offices, list them. If your workplace language isn't English, please specify it. It's suggested, but not required, to include the country/region; "Redmond, WA, USA" is clearer for international candidates.]
\*\*Remote:\*\* [Do you offer the option of working remotely? If so, do you require employees to live in certain areas or time zones?]
\*\*Visa Sponsorship:\*\* [Does your company sponsor visas?]
\*\*Description:\*\* [What does your company do, and what are you hiring C++ devs for? How much experience are you looking for, and what seniority levels are you hiring for? The more details you provide, the better.]
\*\*Technologies:\*\* [Required: what version of the C++ Standard do you mainly use? Optional: do you use Linux/Mac/Windows, are there languages you use in addition to C++, are there technologies like OpenGL or libraries like Boost that you need/want/like experience with, etc.]
\*\*Contact:\*\* [How do you want to be contacted? Email, reddit PM, telepathy, gravitational waves?]
Extra Rules For Third-Party Recruiters
--------------------------------------
Send modmail to request pre-approval on a case-by-case basis. We'll want to hear what info you can provide (in this case you can withhold client company names, and compensation info is still recommended but optional). We hope that you can connect candidates with jobs that would otherwise be unavailable, and we expect you to treat candidates well.
Previous Post
-------------
* [C++ Jobs - Q4 2025](https://www.reddit.com/r/cpp/comments/1ny88qc/c_jobs_q4_2025/)
[reddiquette]: https://support.reddithelp.com/hc/en-us/articles/205926439-Reddiquette
https://redd.it/1q18ynb
@r_cpp
Free real-Time Collaborative Online IDE for web
I am looking for free web IDEs that is used for groups, where members can see and fix or change it LIVE, but it also displays username of those who change recently.
I will be very grateful for anyone find out what I am looking for!!!
AND PLS DON'T DOWNVOTE, MY POST WILL DISAPPEAR.
https://redd.it/1q2tq3c
@r_cpp
SIMD with more than one argument, multiple translation units, ABI
https://pseyfert.codeberg.page/2025/12/simd-with-more-than-one-argument/
https://redd.it/1q2adhg
@r_cpp
Logfault v0.8.5 is released
https://lastviking.eu/logfault_v0.8.5.html
https://redd.it/1q1xpbg
@r_cpp
MayaFlux 0.1.0: A Digital-Native Substrate for Multimedia Computation
Hello r/cpp folks,
I am very excited to announce the initial release of my new creative multimedia programming framework. Here is a short release text, you can find the full context on the [website](https://mayaflux.org/releases/)
MayaFlux 0.1.0 is a C++20/23 infrastructure built to replace the 1980s-era architectures still underlying modern creative coding tools. Built with 15 years of interdisciplinary practice and DSP engineering, it departs from the "analog metaphors" that have constrained digital creativity since the 1980s. MayaFlux does not simulate oscillators or patch cables; it processes unified numerical streams through lock-free computation graphs.
## The Death of Analog Metaphor
Traditional tools (DAWs, visual patchers) rely on legacy pedagogical metaphors. MayaFlux rejects these in favor of computational logic. In this framework, **audio, visuals, and control data are identical.** Every sample, pixel, and parameter is a double-precision floating-point number. This eliminates the artificial boundaries between domains. A single unit can output audio, trigger GPU compute shaders, and coordinate temporal events in the same processing callback without conversion overhead.
## Technical Core: Lock-Free & Deterministic
Building on C++20, MayaFlux utilizes `atomic_ref` and compare-exchange operations to ensure thread safety without mutexes. You can restructure complex graphs or inject new nodes while audio plays -> no glitches, no dropouts, and no contentions. The state promise ensures every node processes exactly once per cycle, regardless of how many consumers it has, enabling true multi-rate adaptation (Audio, Visual, and Custom rates) within a unified graph.
## Lila: Live C++ via LLVM JIT
One of MayaFlux's most transformative features is the **Lila JIT system**. Utilizing LLVM 21+, Lila allows for full C++20 syntax evaluation (including templates and `constexpr`) in real-time. There is no "application restart" or "compilation wait." You write C++ code, hit evaluate, and hear/see the results within one buffer cycle. Live coding no longer requires switching to a "simpler" interpreted language; you have the full power of the C++ compiler in the hot path.
## Graphics as First-Class Computation
Unlike tools where graphics are a "visualization" afterthought, MayaFlux treats the **Vulkan 1.3** pipeline with the same architectural rigor as audio DSP. The graphics pipeline shares the same lock-free buffer coordination and node-network logic. Whether you are driving vertex displacement via a recursive audio filter or mapping particle turbulence to a high-precision phasor, the data flow is seamless and low-level.
## Temporal Materiality
By utilizing **C++20 Coroutines**, MayaFlux turns Time into a compositional material. Through the `co_await` keyword, developers can suspend logic on sample counts, frame boundaries, or predicates. This eliminates "callback hell" and allows temporal logic to be written exactly how it is imagined: linearly and deterministically.
## Who is it for?
MayaFlux is infrastructure, not an application. It is for:
- **Creative Technologists** hitting the limits of Processing or Max/MSP.
- **Researchers** needing direct buffer access and novel algorithm implementation.
- **Developers** seeking low-level GPU/Audio control without framework-imposed boundaries.
The substrate is ready. Visit **mayaflux.org** to start sculpting data.
## A quick teaser
```cpp
#pragma once
#define MAYASIMPLE
#include "MayaFlux/MayaFlux.hpp"
void settings() {
// Low-latency audio setup
auto& stream = MayaFlux::Config::get_global_stream_info();
stream.sample_rate = 48000;
}
void compose() {
// 1. Create the bell
auto bell = vega.ModalNetwork(
12,
220.0,
ModalNetwork::Spectrum::INHARMONIC)[0]
| Audio;
// 2. Create audio-driven logic
auto source_sine = vega.Sine(0.2, 1.0f); // 0.2 Hz slow oscillator
static double last_input = 0.0;
auto
Swapping two blocks of memory that reside inside a larger block, in constant memory
https://devblogs.microsoft.com/oldnewthing/20260101-00/?p=111955
https://redd.it/1q1r6wv
@r_cpp
I created a remote control for your pc
http://trackpad.online
https://redd.it/1q1n85h
@r_cpp
Is modules thought to work seamlessly with external dependencies using #import
Let's say I want to convert my project to use modules instead of #includes. So I replace every #include <vector> with import <vector>?
What happens with all my external dependencies using #include <vector>?
Does this cause conflicts in some way, or does it work seamlessly?
https://redd.it/1q1ekad
@r_cpp
C++ Show and Tell - January 2026
Happy new year!
Use this thread to share anything you've written in C++. This includes:
* a tool you've written
* a game you've been working on
* your first non-trivial C++ program
The rules of this thread are very straight forward:
* The project must involve C++ in some way.
* It must be something you (alone or with others) have done.
* Please share a link, if applicable.
* Please post images, if applicable.
If you're working on a C++ library, you can also share new releases or major updates in a dedicated post as before. The line we're drawing is between "written in C++" and "useful for C++ programmers specifically". If you're writing a C++ library or tool for C++ developers, that's something C++ programmers can use and is on-topic for a main submission. It's different if you're just using C++ to implement a generic program that isn't specifically about C++: you're free to share it here, but it wouldn't quite fit as a standalone post.
Last month's thread: https://www.reddit.com/r/cpp/comments/1pbglr2/c_show_and_tell_december_2025/
https://redd.it/1q3m9n1
@r_cpp
How can you swap two adjacent blocks of memory using only forward iterators?
https://devblogs.microsoft.com/oldnewthing/20260102-00/?p=111958
https://redd.it/1q3hfz9
@r_cpp
Taskflow v4.0 released! Thank you for your support! Happy New Year!
https://github.com/taskflow/taskflow
https://redd.it/1q1jkbz
@r_cpp
MayaFlux 0.1.0: A Digital-Native Substrate for Multimedia Computation
Hello r/cpp folks,
I am very excited to announce the initial release of my new creative multimedia programming framework. Here is a short release text, you can find the full context on the [website](https://mayaflux.org/releases/) or the [git repo](https://github.com/MayaFlux/MayaFlux)
MayaFlux 0.1.0 is a C++20/23 infrastructure built to replace the 1980s-era architectures still underlying modern creative coding tools. Built with 15 years of interdisciplinary practice and DSP engineering, it departs from the "analog metaphors" that have constrained digital creativity since the 1980s. MayaFlux does not simulate oscillators or patch cables; it processes unified numerical streams through lock-free computation graphs.
# The Death of Analog Metaphor
Traditional tools (DAWs, visual patchers) rely on legacy pedagogical metaphors. MayaFlux rejects these in favor of computational logic. In this framework, **audio, visuals, and control data are identical.** Every sample, pixel, and parameter is a double-precision floating-point number. This eliminates the artificial boundaries between domains. A single unit can output audio, trigger GPU compute shaders, and coordinate temporal events in the same processing callback without conversion overhead.
# Technical Core: Lock-Free & Deterministic
Building on C++20, MayaFlux utilizes `atomic_ref` and compare-exchange operations to ensure thread safety without mutexes. You can restructure complex graphs or inject new nodes while audio plays -> no glitches, no dropouts, and no contentions. The state promise ensures every node processes exactly once per cycle, regardless of how many consumers it has, enabling true multi-rate adaptation (Audio, Visual, and Custom rates) within a unified graph.
# Lila: Live C++ via LLVM JIT
One of MayaFlux's most transformative features is the **Lila JIT system**. Utilizing LLVM 21+, Lila allows for full C++20 syntax evaluation (including templates and `constexpr`) in real-time. There is no "application restart" or "compilation wait." You write C++ code, hit evaluate, and hear/see the results within one buffer cycle. Live coding no longer requires switching to a "simpler" interpreted language; you have the full power of the C++ compiler in the hot path.
# Graphics as First-Class Computation
Unlike tools where graphics are a "visualization" afterthought, MayaFlux treats the **Vulkan 1.3** pipeline with the same architectural rigor as audio DSP. The graphics pipeline shares the same lock-free buffer coordination and node-network logic. Whether you are driving vertex displacement via a recursive audio filter or mapping particle turbulence to a high-precision phasor, the data flow is seamless and low-level.
# Temporal Materiality
By utilizing **C++20 Coroutines**, MayaFlux turns Time into a compositional material. Through the `co_await` keyword, developers can suspend logic on sample counts, frame boundaries, or predicates. This eliminates "callback hell" and allows temporal logic to be written exactly how it is imagined: linearly and deterministically.
# Who is it for?
MayaFlux is infrastructure, not an application. It is for:
* **Creative Technologists** hitting the limits of Processing or Max/MSP.
* **Researchers** needing direct buffer access and novel algorithm implementation.
* **Developers** seeking low-level GPU/Audio control without framework-imposed boundaries.
The substrate is ready. Visit **mayaflux.org** to start sculpting data.
# A quick teaser
```cpp
#pragma once
#define MAYASIMPLE
#include "MayaFlux/MayaFlux.hpp"
void settings() {
// Low-latency audio setup
auto& stream = MayaFlux::Config::get_global_stream_info();
stream.sample_rate = 48000;
}
void compose() {
// 1. Create the bell
auto bell = vega.ModalNetwork(
12,
220.0,
ModalNetwork::Spectrum::INHARMONIC)[0]
| Audio;
// 2. Create
Partial implementation of P2826 "Replacement functions"
https://compiler-explorer.com/z/3Ka6o39Th
https://redd.it/1q361b7
@r_cpp
When std::shared_mutex Outperforms std::mutex: A Google Benchmark Study on Scaling and Overhead
https://techfortalk.co.uk/2026/01/03/when-stdshared_mutex-outperforms-stdmutex-a-google-benchmark-study/#Performance-comparison-std-mutex-vs-std-shared-mutex
https://redd.it/1q31yxg
@r_cpp
Are memory leaks that hard to solve?
I have been coding in cpp for the last year (not regularly) and don’t have any professional experience. Why are memory leaks so hard to solve? If we use some basic rules and practices we can avoid them completely.
1) Use smart pointers instead of raw pointers
2) Use RAII, Rule of 5/3/0
I might be missing something but I believe that these rules shouldn’t cause memory related issues (not talking about concurrency issues and data races)
https://redd.it/1q2n7sg
@r_cpp
C++ Show and Tell - December 2025
Use this thread to share anything you've written in C++. This includes:
* a tool you've written
* a game you've been working on
* your first non-trivial C++ program
The rules of this thread are very straight forward:
* The project must involve C++ in some way.
* It must be something you (alone or with others) have done.
* Please share a link, if applicable.
* Please post images, if applicable.
If you're working on a C++ library, you can also share new releases or major updates in a dedicated post as before. The line we're drawing is between "written in C++" and "useful for C++ programmers specifically". If you're writing a C++ library or tool for C++ developers, that's something C++ programmers can use and is on-topic for a main submission. It's different if you're just using C++ to implement a generic program that isn't specifically about C++: you're free to share it here, but it wouldn't quite fit as a standalone post.
Last month's thread: https://www.reddit.com/r/cpp/comments/1olj18d/c_show_and_tell_november_2025/
https://redd.it/1pbglr2
@r_cpp
C++20 Features Explained: Modules, Concepts, Ranges, and Coroutines
https://youtu.be/H9laXhzkKVM
https://redd.it/1q2qcfl
@r_cpp
Are memory leaks that hard to solve?
I have been coding in cpp for the last year (not regularly) and don’t have any professional experience. Why are memory leaks so hard to solve? If we use some basic rules and practices we can avoid them completely.
1) Use smart pointers instead of raw pointers
2) Use RAII, Rule of 5/3/0
I might be missing something but I believe that these rules shouldn’t cause memory related issues (not talking about concurrency issues and data races)
https://redd.it/1q2n7sg
@r_cpp
logic = vega.Logic([](double input) {
// Arhythmic: true when sine crosses zero AND going positive
bool crossed_zero = (last_input < 0.0) && (input >= 0.0);
last_input = input;
return crossed_zero;
});
source_sine >> logic;
// 3. When logic fires, excite the bell
logic->on_change_to(true, [bell](auto& ctx) {
bell->excite(get_uniform_random(0.5f, 0.9f));
bell->set_fundamental(get_uniform_random(220.0f, 1000.0f));
});
// 4. Graphics (same as before)
auto window = MayaFlux::create_window({ "Audio-Driven Bell", 1280, 720 });
auto points = vega.PointCollectionNode(500) | Graphics;
auto geom = vega.GeometryBuffer(points) | Graphics;
geom->setup_rendering({ .target_window = window });
window->show();
// 5. Visualize: points grow when bell strikes (when logic fires)
MayaFlux::schedule_metro(0.016, [points]() {
static float angle = 0.0f;
static float radius = 0.0f;
if (last_input != 0) {
angle += 0.5f; // Quick burst on strike
radius += 0.002f;
} else {
angle += 0.01f; // Slow growth otherwise
radius += 0.0001f;
}
if (radius > 1.0f) {
radius = 0.0f;
points->clear_points();
}
float x = std::cos(angle) * radius;
float y = std::sin(angle) * radius * (16.0f / 9.0f);
float brightness = 1.0f - (radius * 0.7f);
points->add_point(Nodes::GpuSync::PointVertex {
.position = glm::vec3(x, y, 0.0f),
.color = glm::vec3(brightness, brightness * 0.8f, 1.0f),
.size = 8.0f + radius * 4.0f });
});
}
```
https://redd.it/1q1uuok
@r_cpp
Every LLM hallucinates that std::vector deletes elements in a LIFO order
https://am17an.bearblog.dev/every-llm-hallucinates-stdvector-deletes-elements-in-a-lifo-order
https://redd.it/1q1syp2
@r_cpp
coco: a simple stackless, single-threaded, and header-only C++20 coroutine library
http://luajit.io/posts/coco-cpp20-coroutine/
https://redd.it/1q1ntai
@r_cpp
Taskflow v4.0 released! Thank you for your support! Happy New Year!
https://github.com/taskflow/taskflow
https://redd.it/1q1jkbz
@r_cpp
I built a C++ library for fetching satellite data from N2YO (with Python bindings)
Hello everyone,
I've built a C++ library that wraps N2YO's APIs for fetching satellite TLEs, positions, pass predictions and what satellites are currently above. It can also be built with Python bindings if you prefer.
I hope some of you will find this useful.
Thanks!
https://github.com/wstagg/OrbitFetcher
https://redd.it/1q1eyex
@r_cpp