Thank you so much for this link, this is extremely interesting and it really makes me wonder, consciously, I have never read this construction online before, but is this because I actually haven't seen it, or did I subconsciously write it off as an abbreviation or a typo. Maybe there is some analysis of how this construction gets used online, too, which might reveal some linguistic patterns of internet communities.
It's funny how people assume Dehian/Ubuntu's ice cold release schedule is the norm, when the rest of us have been enjoying rolling releases and timely, stress-free (easy rollback) updates with NixOS and Arch back in the days. It's been at 10+ years now.
Ha, ha! I thought the same thing: LLM slop. But soon I remembered having seen this Linotype ad before. It's a genuine image. Almost 140 years ago, some human writer came up with short, punchy copy.
Look what these AI companies have done to us. We see the shadow of slop everywhere.
Using '=' for both assignment and comparison is awkward when parsing incomplete code. Consider e.g.:
j = 5;
The user starts writing (<|> is the cursor position):
i = <|>
j = 5;
This is a valid expression (i is a boolean). But the user probably intends to finish writing something like:
i = 0;
j = 5;
So in the intermediate state we would like to emit a single warning about an incomplete statement. But since it is valid as written, we instead end up warning about e.g. j being unbound.
