Hacker News: arcadialeak

New comment by arcadialeak in "The beauty and simplicity of the good old C-style void* in C++"

arcadialeak — Tue, 09 Jun 2026 10:36:30 +0000

char* is an exception to strict aliasing rules of C++ precisely to facilitate the author's use case. You would still need a reinterpret_cast to make it work, but it's actually good because it makes the intent clearer, and the cast would have still happened either way to read the raw bytes.

New comment by arcadialeak in "Rapira (Рапира) – Soviet programming language interpreter"

arcadialeak — Thu, 28 May 2026 09:59:07 +0000

There is also an independent open-source interpreter for 1C language (which is to this day reported to be extensively used in Russian enterprise) implemented in C#. I haven't tried it myself, but just though that it's also worth mentioning here as the project seems to be actively worked on: https://github.com/evilbeaver/onescript

New comment by arcadialeak in "C constructs that still don't work in C++"

arcadialeak — Mon, 25 May 2026 06:44:51 +0000

> std::string_view or std::span should be used instead

That is for when the owner is a std::string or an owning range respectively. But a raw pointer does still make sense as a non-owning view over a single element, doesn't it? I'm new to C++ so I might be wrong.

New comment by arcadialeak in "Neoclassical C++: segmented iterators revisited"

arcadialeak — Sun, 24 May 2026 10:11:36 +0000

Why does any mention of C++ nowadays turn into a Rust debate? These can coexist even in a single project via C ABI. Also, despite the vast syntax and semantic differences, an experienced dev will be able to apply most of their knowledge from one to the other.

New comment by arcadialeak in "Neoclassical C++: segmented iterators revisited"

arcadialeak — Sun, 24 May 2026 10:05:05 +0000

Since you are already making use of LLMs, you could also ask questions about the code that it produces. I've been asking Google's AI overview and Deepseek while doing my first ever C++26 project, usually not to produce any code but to give advice or list possible approaches to implementing a feature. It's a very slow path, to the point that my project has currently more git commits than lines of code, but I'm convinced that it will pay off in the long run.