> On Jul 21, 2017, at 8:57 AM, Joe Groff <jgr...@apple.com> wrote: > > > > On Jul 20, 2017, at 12:54 PM, Chris Lattner via swift-dev > <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote: > >> >>> On Jul 19, 2017, at 1:23 PM, Robert Widmann via swift-dev >>> <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote: >>> >>> Hello all, >>> >>> The SwiftExperimental >>> <https://github.com/apple/swift/blob/master/stdlib/internal/SwiftExperimental/SwiftExperimental.swift> >>> 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. >>> >>> I would like to remove this library and target from the project, >> >> +1 > > Is there any bug or source compatibility signal to glean from maintenance > changes?
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. 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. -Chris
_______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
