#include <stdio.h>
int typedef[[]]$;
int main($[[]]$) {
[[]]$:&&$&&$&&puts("hello world");
}
Okay…
And it works.
#include <stdio.h>
int typedef[[]]$;
int main($[[]]$) {
[[]]$:&&$&&$&&puts("hello world");
}
Okay…
And it works.
Most C++ codebases aren't getting rewritten in Rust - but that doesn't mean the two can't work together.
At Oxidize 2026, @nicofee and Nicolas Qiu Guichard (@kdab) run a practical workshop on Rust/C++ interop using CXX: calling Rust from C++ and vice versa, integrating a Rust library into a CMake project, and pulling a C++ library into a Cargo build.
🔗 https://oxidizeconf.com/sessions/rust_and_c_plus_plus_can_be_friends
#Oxidize2026 #RustLang #CPlusPlus #Interop #CXX #SystemsProgramming
Choosing between Zngur and CXX for Rust/C++ interoperability?
This detailed comparison explores their design philosophies, container support, trait objects, async capabilities, build systems, and real-world tradeoffs.
Full write-up: https://www.kdab.com/weighing-up-zngur-and-cxx-for-rustc-interop/
We use std::expected.
The Ubuntu image used by our GitHub workflow only comes with Clang 16.
Clang 16 has some sort of issue with including the <expected> header.
Tried to force -libc++ which apparently would make it work. Could not for the life of me get CMake to pass that to Clang.
Then spent like two hours trying to have the GitHub runner install and use Clang 22 instead.
Keep pushing to main to run the workflow, rip our git history.
This is not very fun 🥹
Are you one of the 10'000s of #CXX #Python developers using #pybind11? Do you care about great #autodocs and #autocompletion in #interactive workflows?
The pybind11-stubgen project seeks support in #maintaining it! We #pybind11 maintainers would move it to the #pybind mainline org, but we need a community to help support the .pyi stub generator <3
Chime in here:
https://github.com/sizmailov/pybind11-stubgen/issues/244
std::move doesn't move anything: A deep dive into Value Categories
https://0xghost.dev/blog/std-move-deep-dive/
Anyone have a recommendation for a small (ideally single-file?) C++ Markdown parser library?
I have some Markdown files that I would love to export to various other formats, and don't want to reinvent the wheel if I don't have to. I don't need any support for HTML in Markdown.
Basically I'd love to feed Markdown into a function and be called back for each element (header, paragraph, link etc.), kinda like SAX does for XML?