<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Feb 12, 2016, at 2:24 PM, Philip Reames <<a href="mailto:listmail@philipreames.com" class="">listmail@philipreames.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><blockquote cite="mid:ECBA85B8-8254-4001-9003-6C4CC6A7B219@apple.com" type="cite" class=""><div class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;" class=""><div class=""><div class=""><br class="">
</div>
<div class="">That said, both of those patches are
irrelevant to the discussion, because Argyrios removed
the swift header and replaced it with the LLVM header
when he checked it in.</div>
</div>
</div>
</div>
</blockquote>
<br class="">
</div>
<div class="">Incidentally and unrelatedly, the Swift repo has a bunch of
other generally useful “ADT like” support stuff:</div>
<div class=""><a moz-do-not-send="true" href="https://github.com/apple/swift/tree/master/include/swift/Basic" class="">https://github.com/apple/swift/tree/master/include/swift/Basic</a></div>
<br class="">
<div class="">If folks are interested in seeing any parts of it go
up to LLVM, I’d love to see that happen.</div>
</blockquote>
I'd love to see relevant pieces moved over - provided we actually
use them in LLVM - but we need to make sure we dot the "i"s and
cross the "t"s on the licensing part. Tedious, but necessary.<br class=""></div></div></blockquote><br class=""></div><div>Yes yes, you don’t need to convince me about the merits of doing things right from a licensing perspective, seriously. :-)</div><div><br class=""></div><div>My question is whether there were any specific things people would make sense and people would *want* sunk down to LLVM either ADT, or other things in Swift. If there is an interest, we can make sure the right licensing things happens.</div><div><br class=""></div><div>-Chris</div><br class=""></body></html>