I think I like it, The multi-line \\ I'm not so sure about, but it means you can indent multi-line fields without screwing up the content. I guess it's only when manually creating entries that you get annoyed by typing the same characters over and over.
I also quite like the statement
Alpha, using Ziggy now means participating in its development.
It is neither, "go-away, it's not ready", nor boldly proclaiming to be more than it is. It encourages engagement.
Double-backslash for multiline literals is standard Zig and it takes a bit of getting used to.
I suspect I'll always find it ever-so-slightly unsatisfying because I really want the token to be `\\ `, and it's just `\\`. I don't want those backslashes touching my text!
It's probably the better rule, I say, gritting my teeth slightly, because if you want the text indented, let's say four spaces, making sure it's actually five is annoying and easy to forget. But ugh I don't like looking at unindented multi-line Zig text. Imagine leaving no space between `//` and a comment, I would never. Never!
> Imagine leaving no space between `//` and a comment, I would never. Never!
I usually do this when I out-comment single lines of code. That way I can grep for `//[^ ]` to find lines that are out-commented code, as opposed to being actual comments for humans.
It also helps the readability in the case where a comment for humans is followed by out-commented code, to distinguish where the comment for human ends.
In the language I've implemented, I use significant whitespace for multiline strings and no leader is necessary. Having a leader almost defeats the purpose of multiline string syntax for me.
I also quite like the statement
Alpha, using Ziggy now means participating in its development.
It is neither, "go-away, it's not ready", nor boldly proclaiming to be more than it is. It encourages engagement.