<div dir="ltr">I ran clang-format because the file has many indentation errors. I've noticed that that would also change the table layout but I thought that that was not really bad.<div><br></div><div>It looks like there's no way to tell clang-format to keep this table layout. That means we wouldn't be able to use clang-format on this file, or hand-edit after running clang-format, if we maintain this table layout.<div>
<br></div><div>I can resurrect the table layout and fix only the indentation errors if you want.</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 11, 2013 at 4:19 PM, Nick Kledzik <span dir="ltr"><<a href="mailto:kledzik@apple.com" target="_blank">kledzik@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>The YAML I/O templates are basically tables of how to map yaml keys to struct fields. </div>
<div>I had all them all carefully aligned into two columns (key and field). clang-format</div><div>went and destroyed all that. </div><div><br></div><div>Is there someway to tell clang-format to not change some formatting? </div>
<div>Or should we just not run clang-format blindly?</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>-Nick</div></font></span><div class="im"><br>On Sep 11, 2013, at 3:21 PM, Rui Ueyama <<a href="mailto:ruiu@google.com" target="_blank">ruiu@google.com</a>> wrote:<br>
<blockquote type="cite" dir="auto"><font face="Monaco" size="1">- io.mapRequired("name", keys->_name);<br>- io.mapOptional("ref-name", keys->_refName, StringRef());<br>- io.mapOptional("scope", keys->_scope);<br>
- io.mapRequired("value", keys->_value);<br>+ io.mapRequired("name", keys->_name);<br>+ io.mapOptional("ref-name", keys->_refName, StringRef());<br>+ io.mapOptional("scope", keys->_scope);<br>
+ io.mapRequired("value", keys->_value);<br> }<br></font></blockquote><br></div></div></blockquote></div><br></div>