@matrixstuff3512
Andrei has got to me one of my favorite speakers of any topic
@ethanevans8909
Andrei talks are always so fun
@stratula1
Great speech. Thanks for sharing!
@JohnDlugosz
37:00 Re: Hobbs The ship that Theseus kept swapping parts out of retains its original VIN (Vehicle Identification Number) and is legally Theseus's ship. The one that Hobbs assembled from salvage needs to be registered at the DWPV (Department of Wind-Powered Vehicles) and get a new VIN. To be period-correct, Hobbs would need to obtain a new ΣΠ (Σήμα Πλοίου) at the ΤΠΠΟ (Τμήμα Πλοίων Πνεύματος Όλμων). The definition of "same ship" vs "new ship" is both well-defined and ancient. To show that this is ultimately a matter of definition, consider Microsoft's licensing of Windows. If you swap out one part, like the hard drive, it's recognized as the same PC. But if you swap out three parts—or the wrong part—your license verification might fail, treating it as a new *PC*. (That's my personal experience—Microsoft's exact rules are undocumented and likely change over time.) You used to be able to call Microsoft and explain, "I just got a new hard drive," and they’d restore your license. This shows that there’s no objectively well-defined answer—it’s whatever the bureaucrats (or tech support) have on file. Ultimately, it’s less about an objective set of rules and more about the authority defining that specific case.
@Roibarkan
10:01 Herb Sutter’s talk: https://youtu.be/FNi1-x4pojs (with Alexandrescu cameo)
@jhk578
I like to use reflection but there is something I’m worrying about. Debuggability, I wonder when would we get this thing in a debuggable manner. 2030 seems high expectation😢
@dexterman6361
This talk was great! I was playing around with reflection and when I realized that I couldn't craft functions for the type I was constructing, it felt weird. But I guess something is better than nothing, as C++ is perhaps 26 years too late to the party, any later would be bad.
@hrmIwonder
Oh wow, that's awesome! I'm familiar with the ship of Theseus, but I hadn't heard the part about someone reconditioning the old planks and building a ship out of them. That is fun to think about.. I'd say the new ship with the old wood, is the original ship.
@mishadjukic8904
Very useful talk. The point with identity – the disassembly and reassembly – is powerful indeed. Two comments: - Another version of “Ship of Theseus”: https://www.youtube.com/watch?v=LAh8HryVaeY - On slide 6, the order of arguments of “property” does not match the order of parameters on slide 14 (where definition of “property” is given).
@JohnDlugosz
I think the practicality of generation based on token sequences and constexpr functions can be well-informed by the LISP folks, who use this model, and have used it for decades. Common Lisp predates C++. Scheme is even older.
@nextlifeonearth
I don't think AI will go away anytime soon, but on the short term I see it inhibit the learning of new programmers. If you want to become a prompt kiddy, you can learn with AI. If you want to be a programmer yourself, then stay away from it as long as you can until you understand every line the LLM generates.
@bawbe
gonna be that nerd, pretty sure it's not future subjunctive... I believe it's future perfect... :D @ 8:55
@japedr
queue_injection? Why not code_injection instead?
@driedurchin
This looks a lot like Rust's procedural macros from a usability standpoint, is `queue_injection` fundamentally different from `quote!`?
@abgvedr
UP 😂
@minefun0rus
11:53 Let's be honest, we don't need setters/getters here at all:
```
struct Book {
std::string author;
std::string title;
};
```
@finallyfedupwithpeople
It's a shame that Circle didn't make it into C++
@sunipmukherjee2130
The amount of time we are spending basically turning C++ into Rust amazed me. The moment backwards compatibility is invoked, all of the safety guarantees of these advancements are thrown out. A sad fact this large community doesn’t seem to want to acknowledge.
@alskidan
L-word 😅
@tomkirbygreen