4 ms·
I’d be shocked if jart didn’t know this, but it seems unlikely that an LLM would generate one of these most vexing parses, unless explicitly asked
by legobmw99 2y ago
I’d be shocked if jart didn’t know this, but it seems unlikely that an LLM would generate one of these most vexing parses, unless explicitly asked
- layer8 2y agoGiven all the things that were new to the author in the article, I wouldn’t be shocked at all. There’s just a huge number of things to know, or to have come across.
- jraph 2y agoJustine is proficient in C, she is the author of a libc (cosmopolitan) among other things, like Actually Portable Executables [1]. I would expect her to know C quite well, and that's probably an understatement. [1] https://justine.lol/ape.html https://justine.lol/ape.html
- quietbritishjim 2y agoI think you're thinking of something different to the issue in the parent comment. The most vexing parse is, as the name suggests, a problem at the parsing stage rather than the earlier lexing phase. Unlike the referenced lexing problem, it does't require any hack for compilers to deal with it. That's because it's not really a problem for the compiler; it's humans that find it surprising.