<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Chris,<div> good to see the AbstractType stuff vaporize, but I still have a question, the Type system seems to have</div><div>a "shadow type" system, every user Type created also has a corresponding XYZValType, is the "shadow type"</div><div>system still retained ? It's purpose seems(?) to be for factoring the "unique-ing" logic out of the rest of the type</div><div>system logic, but I'm wondering how much sense that makes (or perhaps I'm not looking at it correctly yet).</div><div><br></div><div>sincerely,</div><div>Peter Lawrence.</div><div><br></div><div><br></div><div><br><div><div>On Jun 25, 2011, at 9:42 AM, <a href="mailto:llvmdev-request@cs.uiuc.edu">llvmdev-request@cs.uiuc.edu</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Monaco; min-height: 16.0px"><br></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Monaco" size="3" style="font: 12.0px Monaco">Once that lands, the constant uniquing is greatly simplified because AbstractType stuff all vaporizes.<span class="Apple-converted-space"> </span>When the branch lands, the constant uniquing maps should all be replaced with folding sets.</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Monaco; min-height: 16.0px"><br></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Monaco" size="3" style="font: 12.0px Monaco">-Chris</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Monaco; min-height: 16.0px"><br></p> </blockquote></div><br></div></body></html>