<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""><div class="gmail_default" style="font-family:verdana,sans-serif">I don't think it's the language's job to enforce preferences here, especially given that holy wars have been fought over indentation (as well as things much less important)</div></div></div></div></div></div></blockquote><div><br class=""></div><div>Actually, as Go shows (and perhaps the Ada's style checking mode a few decades before it), it's precisely the language's job, for exactly that reason. Any bikeshedding that can be avoided, should be. (I'm also enjoying the Standard JavaScript movement of late.)</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""><div class="gmail_default" style="font-family:verdana,sans-serif">Having 3 lines all started by the same number of tabs, but with two having spaces as well for sub-tab-length indentation, should never be an error.</div></div></div></div></div></div></blockquote><div><br class=""></div><div>But to be clear, that wouldn't be an error in my proposed rule, which is, again (I wish I knew how to say this in a simpler way):</div><div><br class=""></div><div>> you want to issue a syntax error if all non-empty lines don't share a common whitespace prefix that entirely covers at least one of the whitespace prefixes.</div><div class=""><br class=""></div><div>A.</div><div><br class=""></div></div></body></html>