SuperV1234

5 ms·

1.
by SuperV1234 4d ago
Taking your advice to heart -- fuck it, I'll make my software and art with generative AI assistence despite any possible backlash :) It's also ironic how the "every programmer I know has basically gone insane over the last co
2.
by SuperV1234 2mo ago
> The main problem, however, was code quality. > The sleight of hand misdirects the reader away from the main way bugs are eliminated: by dedicating engineering resources to it. Perhaps the amount of bugs comes from using a C-like lan
3.
by SuperV1234 3mo ago
Is that all that Mythos did? Did it find any real potential issue, optimization/simplification opportunities, or sparked any thought-provoking discussion within your organization? Or was it purely a net negative experience?
4.
by SuperV1234 4mo ago
How does this compare to frontier models?
5.
by SuperV1234 4mo ago
Data Oriented Design rocks. It was the subject for my CppCon 2025 keynote: https://youtube.com/watch?v=SzjJfKHygaQ
6.
by SuperV1234 4mo ago
It's not that simple. The grandma that would have phoned her nephew to fix the phone will still do the same thing now. She will not have magically switched to querying LLMs after a lifetime of technological illiteracy. The tech-savvy p
7.
by SuperV1234 4mo ago
How'd you infer that I don't find AI useful from my statement? Of course I do. I am merely saying that the argumentation in the "poem" is not specific to AI.
8.
by SuperV1234 4mo ago
And if my router wasn't working 5 years ago, I would have first used a search engine and tried to figure it out on my own. Pretending it's an AI novelty is... disingenuous.
9.
by SuperV1234 4mo ago
I found this quite cringy and an attempt at pulling at one's heartstrings due to the lack of a strong argumentation. I wouldn't have called a friend for a meal plan or to figure out a hiking path 10 years ago, I would have used a
10.
by SuperV1234 4mo ago
Finally, a sane policy.
11.
by SuperV1234 4mo ago
Very interesting, this is the first time I hear about segmented iterators and hierarchical algorithms. I faced a similar issue myself when implementing a chunked vector a la `std::deque`, but opted for callback-based internal iteration, i.e
12.
by SuperV1234 4mo ago
Boxed, and needs complex incantations to avoid the boxing. Meh.
13.
by SuperV1234 4mo ago
That's a strange dismissal. `Optional<T>` isn't "perceived" safety -- it eliminates a whole category of bugs (null dereferences, uninitialized reads) at the type-system level, with zero runtime overhead versus a ra
14.
by SuperV1234 4mo ago
So? The original argument was about the "ugly" syntax that the user didn't want to interact with nor read. I proved that there's no need to do so to consume reflection utils.
15.
by SuperV1234 4mo ago
Alright, I'll bite. This is my `sf::base::Optional<T>` template class, a lightweight replacement for `std::optional` with same semantics: https://github.com/vittorioromeo/VRSFML/blob/master/inc
16.
by SuperV1234 4mo ago
I'm bullish on LLM-assisted development but this is just a very stupid way of performing such a critical migration.
17.
by SuperV1234 4mo ago
That's just false. Templates are not slow to compile at all, and you can selectively pick TUs where they're instantiated. My entire VRSFML codebase compiles from scratch in ~4s and I liberally use C++ features, I just avoid the St
18.
by SuperV1234 4mo ago
This is a myth, C++ is not inherently slow to compile. It's the standard library that is very bloated and the main culprit for slow compilation.
19.
by SuperV1234 4mo ago
Utter BS. Compilation times matter for productivity, developer motivation, iteration speed, CI turnaround time, and so on. I'm sure you wouldn't say "it doesn't matter how long it takes to compile" it if took days
20.
by SuperV1234 4mo ago
No, it objectively isn't objective.
21.
by SuperV1234 4mo ago
Package? We're suggesting to copy paste 5 lines and stick them into a header.
22.
by SuperV1234 4mo ago
#include "to_enum_string.h" You don't have to understand it to use it. Even then, it's not that hard to understand, it just looks unfamiliar.
23.
by SuperV1234 4mo ago
The parent comment is quite clear: > Why do I have to be familiar with all those weird symbols just to do a trivial thing ? And my answer demonstrates that you do not have to.
24.
by SuperV1234 4mo ago
It works generally, but not with expansion statements. See section 3.2 here: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p13... It seems that this is being worked on, and eventuall
25.
by SuperV1234 4mo ago
To be honest there are ways to make that much nicer. I believe that if you use recursive macros using the VA_OPT feature, you should be able to provide enumerators directly to define enum as a list. The underlying machinery implementation i
26.
by SuperV1234 4mo ago
By your logic we shouldn't ever use external libraries. PFR has given us reflection since C++14. I also don't think the Standard Library is particularly well-defined nor well-implemented, as demonstrated by the atrocious compila
27.
by SuperV1234 4mo ago
It is kind of weird at first but the reason is that `std::vector` requires heap allocation and transient allocations are not allowed in `constexpr` contexts. The purpose of `std::define_static_array` is to promote the storage of the vector
28.
by SuperV1234 4mo ago
This cost is not significant nowadays, it's the frontend/parsing time. You can also use `#pragma once` which works everywhere, is nicer, and technically needs less work by the compiler, but compilers have optimized for include gua
29.
by SuperV1234 4mo ago
It's a fair comparison. The parent comment isn't showing the compiler source code for the built-in reflection mechanisms. You won't have to care about ^^ and [:X:] if you just want to consume reflection-based utils, which was
30.
by SuperV1234 4mo ago
C++: enum Color { red, green, blue }; auto name = to_enum_string(Color::Red); // "Red"

More ›