My coworker added some syntax in an in-house language that I otherwise designed; against my advice, it’s ambiguous, so it requires a number of special cases to handle correctly, and has been a source of several bugs—I wish they’d trusted me more when I said I know notation design
Conversation
Replying to
No, it’s pretty established, so I do have to continue supporting it, but at my behest & design we have a versioning policy, so I can introduce a new feature, add a warning for the old one, and maybe later remove it
1
1
Mostly this is used as a target language, and for debug output, so it’s not *super* important apart from the edge-case bugs that cause minor delays (e.g., the output of the pretty-printer won’t parse)
It’s just aesthetically unsatisfying, hah
1
1
Show replies