Skip to content
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

[SR-1966] Move lazy collection wrappers into an enum "namespace" #44575

Open
gribozavr opened this issue Jul 1, 2016 · 1 comment
Open

[SR-1966] Move lazy collection wrappers into an enum "namespace" #44575

gribozavr opened this issue Jul 1, 2016 · 1 comment
Labels
affects ABI Flag: Affects ABI bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. standard library Area: Standard library umbrella

Comments

@gribozavr
Copy link
Collaborator

Previous ID SR-1966
Radar rdar://problem/27123183
Original Reporter @gribozavr
Type Bug
Additional Detail from JIRA
Votes 0
Component/s Standard Library
Labels Bug, AffectsABI
Assignee None
Priority Medium

md5: 032b79d5f9c113d815751ffeab4a626d

Issue Description:

Lazy collection wrappers are almost implementation details of the lazy subsystem. In general we don’t want users to use them in the API signatures.

Because they are so not important to mention by name, we could move them into an empty enum “namespace”:

LazyMapCollection => LazyCollections.MapView

etc.

@airspeedswift
Copy link
Member

This is possibly going to be rendered redundant by the refactoring of the lazy containers enabled by conditional conformance. Though there might still be implementation details remaining that deserve to be hidden.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects ABI Flag: Affects ABI bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. standard library Area: Standard library umbrella
Projects
None yet
Development

No branches or pull requests

2 participants