-
Notifications
You must be signed in to change notification settings - Fork 1.4k
adopt swift-collections #3595
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adopt swift-collections #3595
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
/* | ||
This source file is part of the Swift.org open source project | ||
|
||
Copyright (c) 2021 Apple Inc. and the Swift project authors | ||
Licensed under Apache License v2.0 with Runtime Library Exception | ||
|
||
See http://swift.org/LICENSE.txt for license information | ||
See http://swift.org/CONTRIBUTORS.txt for Swift project authors | ||
*/ | ||
|
||
import OrderedCollections | ||
|
||
public typealias OrderedDictionary = OrderedCollections.OrderedDictionary | ||
public typealias OrderedSet = OrderedCollections.OrderedSet | ||
Comment on lines
+11
to
+14
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What's the benefit of this file (no There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. good point. @neonichu @abertelrud do you think re-exporting common modules like swift-collections, swift-system would make sense, or prefer individual imports? I am on the fence. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Personally not a fan of re-exporting, it might also hurt incremental builds? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I strongly prefer individual imports, to make it clear what's being used. Tooling should ideally help add those where needed (the effort of having to add the individual imports is usually the main argument against it). So I agree with neonichu on this. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It also makes it clear that the standard ordered collections are being used rather than something specific to TSC. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Unless I'm reading it wrong, it seems like the general opinion is not to import |
Uh oh!
There was an error while loading. Please reload this page.