<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 Jul 21, 2017, at 8:57 AM, Joe Groff <<a href="mailto:jgroff@apple.com" class="">jgroff@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class=""></div><div class=""><br class=""></div><div class=""><br class="">On Jul 20, 2017, at 12:54 PM, Chris Lattner via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><br class=""><div class=""><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 class="">+1</div></div></blockquote><br class=""><div class="">Is there any bug or source compatibility signal to glean from maintenance changes? </div></div></div></blockquote></div><br class=""><div class="">I doubt it. These are not widely used APIs, so even if they broke, it wouldn’t matter. Keeping the source compatibility suite focused on real world code makes the most sense IMO.</div><div class=""><br class=""></div><div class="">I’d suggest just nuking SwiftExperimental. If someone cares enough to move them to a new SPM package somewhere, then they can do that at any time - the code is always available in git history.</div><div class=""><br class=""></div><div class="">-Chris</div><div class=""><br class=""></div></body></html>