Navigation Menu

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-269] Implement ResilienceDomain abstraction #42891

Closed
slavapestov opened this issue Dec 17, 2015 · 2 comments
Closed

[SR-269] Implement ResilienceDomain abstraction #42891

slavapestov opened this issue Dec 17, 2015 · 2 comments
Assignees
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself

Comments

@slavapestov
Copy link
Member

Previous ID SR-269
Radar None
Original Reporter @slavapestov
Type Bug
Status Resolved
Resolution Invalid
Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Bug
Assignee @slavapestov
Priority Medium

md5: 0491a373a73b68bebc35761f2e0c440a

blocks:

  • SR-260 Add availability information to @_fixed_layout attribute
  • SR-257 Resilient value type support -- umbrella bug

Issue Description:

A ResilienceDomain consists of a ResilienceExpansion together with a target deployment version. It is used to answer the question, "can I make layout about this type."

@belkadan
Copy link
Contributor

I don't understand ResilienceExpansion that well, but why would it be part of ResilienceDomain?

@slavapestov
Copy link
Member Author

This bug is not useful since it assumes a specific implementation design. I'm going to close it, we'll derive the right abstractions organically over time.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself
Projects
None yet
Development

No branches or pull requests

2 participants