<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 21, 2020, at 15:46, Evandro Menezes via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">There is a lot of room from improvement in several details of TableGen. However, methinks that changes towards such a goal shouldn't be sneaked in small doses. Then it just adds more inconsistent error reporting to an already inconsistent reporting. If one wants to improve the error reporting in TableGen, let one take it on himself this project, apart from one's other patches.</span><br class="Apple-interchange-newline"></div></blockquote></div><br class=""><div class="">Realistically, replacing all of TableGen’s error reporting in one shot is not going to happen. I don’t see any reason to delay fixing any particular error because all of the others are bad. For TableGen, I’m happy enough when there is an actual error and not an assert.</div><div class=""><br class=""></div><div class="">-Matt</div></body></html>