Fix typo in README: where necessarily -> where necessary #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lattner
added a commit
that referenced
this pull request
Dec 3, 2015
Fix typo in README: where necessarily -> where necessary
lattner
pushed a commit
that referenced
this pull request
Mar 24, 2016
kkdevenda
added a commit
to kkdevenda/swift-evolution
that referenced
this pull request
Aug 1, 2016
DougGregor
added a commit
that referenced
this pull request
Nov 30, 2018
…ointerIfSupported` methods
rjmccall
pushed a commit
that referenced
this pull request
Jun 28, 2019
…#2 Changes from the second reviewed version * The synthesized storage property is always named with a leading `_` and is always `private`. * The `wrapperValue` property has been renamed to `projectedValue` to make it sufficiently different from `wrappedValue`. This also gives us the "projection" terminology to talk about the `$` property. * The projected property (e.g., `$foo`) always has the same access as the original wrapped property, rather than being artificially limited to `internal`. This reflects the idea that, for property wrapper types that have a projection, the projection is equal in importance to the wrapped value.
heckj
pushed a commit
to heckj/swift-evolution
that referenced
this pull request
Sep 1, 2021
Wasm is never written in all uppercase (according to the spec https://webassembly.github.io/spec/core/intro/introduction.html), since Wasm is not an acronym.
kavon
referenced
this pull request
in kavon/swift-evolution
Feb 16, 2023
allow noncopyable types to conform to `Sendable`
Jumhyn
added a commit
that referenced
this pull request
Jun 14, 2023
* Add proposal for init accessors. * Init accessors suggestions (#2) * Expand description of accesses and give a "dictionary storage" example * Make the name of the `newValue` parameter configurable Be consistent with set/willSet/didSet in making the parameter name optional and overridable. * A few clarifications regarding init accessor signatures * Clarify the rules for definite initialization Expand the examples and show the case where virtual and stored-property initialization collide. --------- Co-authored-by: Holly Borla <[email protected]> * Address outstanding proposal comments. * Update the syntax for init accessor effects based on pitch feedback. * Update the first init accessor example to use a custom parameter name. * Add an acknowledgments section for the init accessors proposal. * Update proposals/NNNN-init-accessors.md Co-authored-by: Frederick Kellison-Linn <[email protected]> * Remove the phrase "virtual initialization". * Editorial changes. * Update the Alternatives Considered section with more syntax suggestions from the pitch thread. * Add more commentary on member-wise initializers. * Add a DI example where a property is not initialized on all paths. * Init accessors is SE-0400 --------- Co-authored-by: Doug Gregor <[email protected]> Co-authored-by: Frederick Kellison-Linn <[email protected]> Co-authored-by: Freddy Kellison-Linn <[email protected]>
kubamracek
added a commit
to kubamracek/swift-evolution
that referenced
this pull request
Jan 31, 2024
kubamracek
added a commit
to kubamracek/swift-evolution
that referenced
this pull request
Jan 31, 2024
tbkka
referenced
this pull request
in tbkka/swift-evolution
Feb 28, 2024
Rework Motivation; other smaller edits
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.