<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Nov 30, 2011, at 6:33 PM, David Blaikie wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Slightly related/minor tidyup - should the isType/ValueDependent<br>checks in tryEvaluate/tryEvaluateBool be removed (and possibly<br>replaced with assertions) as they don't seem to do anything - we<br>weren't visiting dependent contexts previously nor are we now.</span></blockquote></div><br><div>I'd be happy with that if we just had CFGBuilder abort up front the construction on raw (uninstantiated) templates. This defensive code is there so that other clients of CFGBuilder (besides AnalysisBasedWarnings) don't get into trouble.</div></body></html>