I wonder whether Swift’s error reporting would improve if we reintroduced explicit line ending markers (doesn’t have to be “;”, could just be the line break plus supporting \ for escaping line breaks that aren’t statement ends).
@uliwitness Explicit line ending would almost certainly require the support of most IDE designers so they can allow for explicit line endings in code. Most would opt for an automatic setting similar to braces matching. Then of course, converting older source to newer line ended source would never be perfect because someone will always run that against code that has already been converted unless the converter is allowed to set a flag at the beginning to id new versus old.
But it would help the debuggers.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!
We adhere to an adapted version of the TootCat Code of Conduct and follow the Toot Café list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators.
Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!