fa
Feedback
C++ - Reddit

C++ - Reddit

رفتن به کانال در Telegram

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

نمایش بیشتر
229
مشترکین
اطلاعاتی وجود ندارد24 ساعت
اطلاعاتی وجود ندارد7 روز
اطلاعاتی وجود ندارد30 روز
آرشیو پست ها
Concept-based Generic Programming - Bjarne Stroustrup - CppCon 2025 https://youtu.be/VMGB75hsDQo https://redd.it/1njqbs1 @r_cpp

{fmt} 12.0 released with optimized FP formatting, improved constexpr and module support and more https://github.com/fmtlib/fmt/releases/tag/12.0.0 https://redd.it/1njijl0 @r_cpp

Looking for feedback on my short C++ coding tips video (made with NotebookLM) https://youtu.be/DtwZzlmYElE https://redd.it/1njd29u @r_cpp

Rust Coreutils Are Performing Worse Than C/C++ based GNU Coreutils in Ubuntu https://news.itsfoss.com/ubuntu-uutils-performance-issues/ https://redd.it/1nirrpt @r_cpp

Meta: Unwritten Rules? Recently there was a post that got deleted with this rationale "AI slop is not welcome on r/cpp. Please stop and think about what you're doing." While I understand the desire to remove AI slop. (disclaimer: I used to do AI programming more than 3 decades ago. And I strongly dislike the current perversion of LLM application.) But I do understand that some AI, like LLMs and general statistical inference (like spell checkers), is useful to many (I couldn't survive without spellchecking for example). Hence the threat of being banned for some assistive AI uses to be a bit dramatic. More importantly, this made me wonder what, if any, other such banning or drastic content moderation rules there are in this forum above the stated ones? \-- Just wondering "out loud". -- (edited to fix a grammar error.. ironic I know) https://redd.it/1nipls9 @r_cpp

Parallel C++ for Scientific Applications: Working With Types https://www.youtube.com/watch?v=F15ixlwyDlA https://redd.it/1nim6dz @r_cpp

Made a CLI tool for ASCII text in C++ Hey everyone! I've been working on my first C++ project and wanted to share it here. It’s a lightweight command-line tool that lets you render text into ASCII art, with support for multiple fonts, a scrolling banner effect and outputting files. I built it mainly to learn C++, and picked up CMake on the way and used CLI11 for argument parsing and toml++ for parsing files. I’d love feedback on the code, CLI design, or any feature suggestions. Contributions, especially in the form of new fonts, are also very welcome. Check it out here! https://redd.it/1nih3wv @r_cpp

Hey guys! Just wanted to know as someone who's 30, would I find it difficult now to start learning code? I've been working construction for a while and honestly I dont wanna do it anymore, ive always been interested in coding but obviously never been able to jump into it. So just looking for some advice or some direction if you dont think its too late. https://redd.it/1nhylcr @r_cpp

I am looking for a decent ide without ai features http://geany.org https://redd.it/1nhrajh @r_cpp

¿Vale la pena publicar mi librería de enteros sin signo “OfUint” en GitHub? Recientemente creé una librería de tipos enteros sin signo llamada **OfUint**, que incluye tamaños no estándar además de los comunes: `OfUint1`, `OfUint2`, `OfUint4`, `OfUint8`, `OfUint16`, `OfUint32`, `OfUint64` y `OfUint128`. 👉 **Ventajas principales:** * En **cálculo masivo**, los tipos pequeños (`OfUint1`, `OfUint2`, `OfUint4`) son más rápidos que `unsigned char` o `unsigned short`. * En **cálculo unitario**, tienen el mismo rendimiento que los nativos, pero con un plus de seguridad. * Se pueden usar exactamente igual que cualquier tipo nativo en C/C++ (`+`, `-`, `*`, etc.). Ejemplo rápido: OfUint4 a = 7; OfUint4 b = 9; OfUint4 c = a * b + 3; // funciona igual que con uint8_t Mi duda es: 👉 ¿Les parece interesante que publique esta librería en GitHub con benchmarks y documentación, o no vale la pena? https://redd.it/1nhtg64 @r_cpp

New C++ Conference Videos Released This Month - September 2025 C++Now 2025-09-01 - 2025-09-07 How to Build a Flexible Robot Brain One Bit at a Time - Ramon Perez - [https://youtu.be/akJznI1eBxo](https://youtu.be/akJznI1eBxo) Zngur - Simplified Rust/C++ Integration - David Sankel - https://youtu.be/k\_sp5wvoEVM Advanced Ranges - Writing Modular, Clean, and Efficient Code with Custom Views - Steve Sorkin - [https://youtu.be/5iXUCcFP6H4](https://youtu.be/5iXUCcFP6H4) 2025-09-08 - 2025-09-14 std::optional — Standardizing Optionals over References - A Case Study - Steve Downey - https://youtu.be/cSOzD78yQV4 Are We There Yet? - The Future of C++ Software Development - Sean Parent - [https://youtu.be/RK3CEJRaznw](https://youtu.be/RK3CEJRaznw) Alex Stepanov, Generic Programming, and the C++ STL - Jon Kalb - https://youtu.be/yUa6Uxq25tQ ACCU Conference 2025-09-08 - 2025-09-14 How to Think Like a Programmer - Connor Brook - [https://youtu.be/aSptXRefE6A](https://youtu.be/aSptXRefE6A) C++ Error Handling Omitted - Roger Orr - https://youtu.be/QXpk8oKiFB8 Building a Career Off-Road - Sherry Sontag, CB Bailey, Callum Piper, Cal Pratt & Daniel Kiss - [https://youtu.be/7d44F6N8eZI](https://youtu.be/7d44F6N8eZI) 2025-09-01 - 2025-09-07 The Hidden Techical Debt Crisis: When Non-Engineers Write Code - Felix Aldam-Gates - https://youtu.be/VXb4n8FjcrE The 10 Essential Features for the Future of C++ Libraries - Mateusz Pusz - [https://youtu.be/K-uzaG9S8bg](https://youtu.be/K-uzaG9S8bg) An Introduction To Go - Dom Davis - https://youtu.be/l36Wqmw2JZo C++ on Sea 2025-09-08 - 2025-09-14 Safe and Readable Code - Monadic Operations in C++23 - Robert Schimkowitsch - [https://youtu.be/fyjJPwkVOuw](https://youtu.be/fyjJPwkVOuw) Missing (and future?) C++ Range Concepts - Jonathan Müller - https://youtu.be/T6t2-i5t1PU Mind the Gap (Between Your Code and Your Toolchain) - Yannic Staudt - [https://youtu.be/iqhbBjcoCnM](https://youtu.be/iqhbBjcoCnM) 2025-09-01 - 2025-09-07 Welcome to v1.0 of the meta::[[verse\]\]! - Inbal Levi - https://youtu.be/Wbe09UFDvvY To Err is Human - Robust Error Handling in C++26 - Sebastian Theophil - [https://youtu.be/A8arWLN54GU](https://youtu.be/A8arWLN54GU) The 10 Essential Features for the Future of C++ Libraries - Mateusz Pusz - https://youtu.be/TJg37Sh9j78 ADC 2025-09-01 - 2025-09-07 Current Approaches and Future Possibilities for Inter Audio Plugin Communication - Janos Buttgereit - [https://youtu.be/YHWdDLi6jgc](https://youtu.be/YHWdDLi6jgc) Keynote: Sonic Cartography - Navigating the Abstract Space-Time of Sound - Carla Scaletti - https://youtu.be/iq75B8EkLv4 https://redd.it/1nhrzq6 @r_cpp

Why did stl algorithms use iterators in interface? This part doesn't make any sense to me, almost 99.9% of time you want to do it on the whole thing but you can't, if just the algorithms were ```cpp template<class Container,class Value> auto find_if(Container const& c,Value value); ``` then I can just do std::vector<int> a; auto it = std::find(a,0); but someone will say "how about if a sub range?!" then the stl should provide `std::subrange` that is just a simple wrapper for template<class It,class Sen = It> struct subrange : private Sen { // for empty senitiel subrange(It begin,Sen end) : Sen(end),_begin(begin) {} It begin(): const { return _begin;} Sen end(): const { return static_cast<Sen&>(*this);} It _begin; }; then if you want a dubrange do std::vector<int> a; auto it = find(subrange(a.begin(),a.end() - 5),0); seems like most logical thing to do, make the common case easy and the less common one still possible and also it allows checks depending on the container for debug builds or speedups like map.lower_bound by using a friend function instead of having to account for both a member function and a free function this annoys generic programming the current stl design is backwards make the common case annoying and the less common one easy. (I also think ranges having still the iterators overloads is a mistake, wish they removed them) https://redd.it/1nhmwhr @r_cpp

How I Learned to Be an Effective Boost Review Manager — My Tips & Templates Hey r/cpp 👋 I recently published a post on my journey as a Boost Review Manager and wanted to share some of the insights that might help others stepping into this role, or even those just curious about how Boost peer reviews tick: How to Be an Effective Boost Review Manager Here’s what you’ll find inside: A breakdown of the Review Manager’s responsibilities—not just technical, but facilitating fair discussion, keeping things structured, and summarizing feedback. Templates & timeline suggestions: announcement emails, reminders, closing notes, and decision reports. (Stuff I wish I had when I first did this.) Reflections on how to balance being supportive to the author while making sure the library meets Boost’s standards (design, docs, maintainability). Why this matters: Boost is hugely influential in C++ — many of its libraries or concepts make their way into the standard. Ensuring the review process is fair, clear, and useful matters not just for the author, but for the community and long-term health of the library ecosystem. Would love to hear from folks who’ve been Review Managers before: What did you do differently than what I describe? What pushed back on your plans? What wisdom would you give new/aspiring Review Managers? If you give it a read, I’d appreciate any feedback, suggestions, or criticism. Thanks! https://redd.it/1nhl4rn @r_cpp

What is the current state of modules for an open source library? Hi there, I'm building a tensor library and have it working to the point where I have some simple models like llama3 or a vision transformer working on cpu. I need to take a decision before continue, and that is if to try to migrate from headers to modules. Since I didn't release the library, nobody is using it and will take my time since kernels are not optimized yet, I'm not attached to current versions of compilers or cmake, and I can use new stuff and some "not so ready" features like modules. I was looking into some posts, but they may be outdated now, and I would like to know your opinion. https://redd.it/1nh5e8c @r_cpp

Why does CMake configuration RelWithDebInfo by default adds "/Ob1" instead of "/Ob2"? I'm posting questions that I have been curious about almost since I first ever used CMake. In short, RelWithDebInfo disables inlining of any function that isn't declared inline. The whole reason (at least for me) of having debug info in the release build is because that allows me to debug the machine code that is mostly same (if not exactly same) as the pure release build. Sure, inlining makes debugging a lot more fun (/s), but what really is the point of debugging a half-optimized code? I would normally either just debug the code with the optimization fully turned off, or the fully optimized code. (What counts as "fully" might be debatable, but I think that's not the point here.) I admit there are situations where I would want to debug half-optimized code (and I ran into such situations several times before), but (1) those cases are pretty rare I think, and (2) even for such cases, I would rather just locally disable optimizations by other means than to disable inlining globally. So I feel like RelWithDebInfo in its current form is almost 100% useless. Rant aside, I found that this exact complaint seems to have repeated many times in various places, yet is not addressed so far. So I'd like to know: - Does anyone really use RelWithDebInfo even with awareness of this pitfall? If so, is it because of its ease of debugging (compared to the fully optimized code), or is it simply because you could bare the inferior performance of RelWithDebInfo and didn't want to bother? - What is/was the rationale behind this design choice? - Is it recognized as an oversight these days (by the CMake developers themselves), or not? - If so, then what's the reason for keeping it as it is? Is it simply the backward-compatibility? If so, then why not just add another default config? https://redd.it/1nh2xx3 @r_cpp

My attempt at learning OpenGL by building a fractal explorer Hey everyone, I've been working on a personal project called FractaVista to get more comfortable with modern C++ and learn OpenGL compute shaders. It's a fractal explorer that uses the GPU for real-time rendering, built with C++17, OpenGL, SDL3, and Dear ImGui. It's definitely still a work in progress, but the code is up on GitHub if you're curious to see how it works or try building it. Any feedback or suggestions would be super appreciated, and a star on the repo if you like the project would mean a lot! ⭐ GitHub Repo: https://github.com/Krish2882005/FractaVista Thanks for checking it out! https://redd.it/1ngxfvn @r_cpp