Swift Evolution is engaged in a war over the multi-line string. While this conversation dates back some time, it has progressively grown more heated in recent days.
@ericasadun Oh yeah, it’s like emacs and vi.
— macshome (@macshome) May 5, 2016
I just want closure. I’m more interested in closure than perfection. My favorite solution to date is the Holdsworth/Royal-Gordon approach:
It is simple. It does not disallow pasted text, with the proper support from Xcode. It can theoretically be applied (and removed) mechanically as you can currently do with commenting.
Its parsing/lexing is simple and already Holdsworthed. (In theory, everything that can be conceptualized in Xcode is nearly Holdsworthed.) And it probably wouldn’t be hard to request an Xcode modification similar to Comment/Uncomment that indents and inserts quotes and toggles back to left-alignment at the initial quote mark.
That the debate rages on remains a mystery to me.
Speaking of Xcode and its commenting support, I am still waiting for better Apple-originated structured documentation commenting. As is, it’s particularly ridiculous to try to introduce sample code blocks without manually spacing and adding in third slashes, let alone proof for spell checking and grammar. But that’s probably a rant better left for another blog post.
For today, I support the Holdsworth/Royal-Gordonians. Viva la quoted resistance!