<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><div><br>On Jul 20, 2017, at 12:54 PM, Chris Lattner via swift-dev <<a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 19, 2017, at 1:23 PM, Robert Widmann 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; line-break: after-white-space;" class="">Hello all,<div class=""><br class=""></div><div class="">The <a href="https://github.com/apple/swift/blob/master/stdlib/internal/SwiftExperimental/SwiftExperimental.swift" class="">SwiftExperimental</a> library’s stated purpose is to be a place where experimental library features could be explored without fear of committing to a stable interface. At least, that was its goal many years ago when significant work on it was last done. Since then, SwiftExperimental has sat untouched except for passing committers that need to alter parts of its implementation for language changes. </div><div class=""><br class=""></div><div class="">I would like to remove this library and target from the project, </div></div></div></blockquote><br class=""></div><div>+1</div></div></blockquote><br><div>Is there any bug or source compatibility signal to glean from maintenance changes? If so, it might be worth moving it to the source compatibility suite. Makes sense to get it out of the main compiler tree, though.</div><div><br></div><div>-Joe</div></body></html>