Yeah, it’s in my edit I realized the same thing. I’m thinking it doesn’t actually really make sense and the real reason is more “the specific way C does it causes a lot of problems so we’re not poking syntax like that with a 10 foot pole” + “it makes writing the parser easier” + maybe a bit of “it makes grepping easier”
- 2 Posts
- 8 Comments
Joined 2 years ago
Cake day: July 16th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
So I think it’s still probably unclear to people why “mix of keywords and identifiers” is bad: it means any new keyword could break backwards compatibility because someone could have already named a type the same thing as that new keyword.
This syntax puts type identifiers in the very prominent position of “generic fresh statement after semicolon or newline”
…though I’ve spent like 10 minutes thinking about this and now it’s again not making sense to me. Isn’t the very common plain “already_existing_variable = 5” also causing the same problem? We’d have to go back to cobol style “SET foo = 5” for everything to actually make it not an issue
You can still be snobby by instead insisting on “fold, scan, iterate”
What is mutually exclusive, though, is reality and China’s “imminent collapse” which has been looming just around the corner for the past 20 years
it’s funny how you can tell at a glance exactly what model generated this image, just based off the background color
at high signal strength LDAC should default to 990kbps… which is kind of ridiculous since it’s so high it’s higher than some lossless codecs, like uncompressed 16-bit 48kHz. (which is higher than standard CD quality)
I tried to edit the ‘highlights’ into a single image, the top is the description of the PR, the middle is a comment replying to another comment
funny how well this fits for both meanings