<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On 24 Jan 2017, at 20:10, Andrew Trick via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I’m sending out a proposal for fundamentally changing SIL. This work feeds into generic code optimization, resilience, semantic ARC, and SIL ownership. This was discussed at length back in October—some info went out on swift-dev—but I realized there hasn’t been a formal proposal. So here it is. I want to make sure enough people have seen this before pushing my PR that puts the infrastructure in place: <a href="https://github.com/apple/swift/pull/6922" class="">https://github.com/apple/swift/pull/6922</a>.</div><div class=""><br class=""></div><div class="">Rendered Proposal: <a href="https://gist.github.com/atrick/38063a90bf4a6ebae05fe83ea9ebc0b7" class="">https://gist.github.com/atrick/38063a90bf4a6ebae05fe83ea9ebc0b7</a></div><div class=""><br class=""></div><div class="">Markdown:</div></div><span id="cid:C86860D7-D6FE-4B9C-9AA0-3E205316CAF6@fritz.box"><silval-proposal-1.md></span><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">-Andy</div></div>
_______________________________________________<br class="">swift-dev mailing list<br class=""><a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-dev<br class=""></div></blockquote></div><br class=""><div class="">I won’t pretend to understand all of the implications of this, but as a newcomer to the codebase I found SILGen (particularly lowering) extremely confusing to unpick.</div><div class=""><br class=""></div><div class="">The simplification and separation described here makes a lot of sense to me, and I believe it would make it easier for myself and others to contribute to the project. As do your comments in the PR about using consistent idioms throughout the compiler.</div><div class=""><br class=""></div><div class="">So as far as those things are considerations, I’m really happy with this proposal.</div><div class=""><br class=""></div><div class="">- Karl</div></body></html>