Minor grammatical fixes to README #3
Merged
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
| @@ -28,7 +28,7 @@ feel and implementation. Swift 3.0 will contain *source-breaking* | |||
| changes from Swift 2.x where necessarily to support these goals. More | |||
| concretely, this release is focused on several key areas: | |||
|
|
|||
| * **Stable ABI**: Stabilize the binary interface (ABI) to guarantee a level of binary compatibility moving forward. This involves finalizing runtime data structures, name mangling, calling conventions, and so on, as well as finalizing some of the details of the language itself that have an impact on its ABI. Stabilizing the ABI also extends to the Standard Library, especially it's data types are core algorithms. Successful ABI stabilization means that applications and libraries compiled with future versions of Swift can interact at a binary level with applications and libraries compiled with Swift 3.0, even if the source language changes. | |||
| * **Stable ABI**: Stabilize the binary interface (ABI) to guarantee a level of binary compatibility moving forward. This involves finalizing runtime data structures, name mangling, calling conventions, and so on, as well as finalizing some of the details of the language itself that have an impact on its ABI. Stabilizing the ABI also extends to the Standard Library; its data types are core algorithms. Successful ABI stabilization means that applications and libraries compiled with future versions of Swift can interact at a binary level with applications and libraries compiled with Swift 3.0, even if the source language changes. | |||
There was a problem hiding this comment.
should it be "its data types and core algorithms"?
lattner
added a commit
that referenced
this pull request
Dec 3, 2015
Minor grammatical fixes to README
rjmccall
pushed a commit
that referenced
this pull request
Jun 14, 2019
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.
stephentyrone
pushed a commit
to stephentyrone/swift-evolution
that referenced
this pull request
Mar 4, 2020
Make `includePrefix = true` the default for integer formatters.
airspeedswift
pushed a commit
that referenced
this pull request
Jul 7, 2021
…om the third review (#1406) * [SE-0304] Replace `TaskGroup.async` with `TaskGroup.addTask`. The use of the adjective `async` for creating new child tasks was too confusing and didn't fit well with the naming guidelines. Instead, use `addTask`, which makes it clear that we are adding a new task into a task group (the result of which is available via `next()`). * [SE-0304] Rename `sleep(_:)` to `sleep(nanoseconds:)`. * [SE-0304] Split out changes due to review #3 * [SE-0304] Rename TaskPriority.default to TaskPriority.medium * [SE-0304] Add (Throwing)?TaskGroup.waitForAll * [SE-0304] Rename `Task.yield()` to `Task.suspend()` * [SE-0304] Make `Task.sleep(nanoseconds:)` throwing on cancellation * Re-schedule review
mattt
pushed a commit
to mattt/swift-evolution
that referenced
this pull request
Aug 17, 2021
…om the third review (swiftlang#1406) * [SE-0304] Replace `TaskGroup.async` with `TaskGroup.addTask`. The use of the adjective `async` for creating new child tasks was too confusing and didn't fit well with the naming guidelines. Instead, use `addTask`, which makes it clear that we are adding a new task into a task group (the result of which is available via `next()`). * [SE-0304] Rename `sleep(_:)` to `sleep(nanoseconds:)`. * [SE-0304] Split out changes due to review swiftlang#3 * [SE-0304] Rename TaskPriority.default to TaskPriority.medium * [SE-0304] Add (Throwing)?TaskGroup.waitForAll * [SE-0304] Rename `Task.yield()` to `Task.suspend()` * [SE-0304] Make `Task.sleep(nanoseconds:)` throwing on cancellation * Re-schedule review
heckj
pushed a commit
to heckj/swift-evolution
that referenced
this pull request
Sep 1, 2021
* Fix a typo * Various typographic fixes
airspeedswift
added a commit
that referenced
this pull request
Jan 11, 2022
* Initial draft * Revise proposal and narrow it to @predatesConcurrency * Add examples and describe @predatesConcurrency protocol behavior * Rename `@predatesConcurrency` to `@preconcurrency` * Clarify that using concurrency features enables Sendable checking. * Simplify from 3 "concurrency checking modes" to 2. We only need "minimal" and "strict"; the other differences are accounted for by the language mode (warnings prior to Swift 6, errors thereafter) and the behavior of the `@preconcurrency` attribute. * Remove an extraneous space * Add links to implementation, toolchains, pitch #3 thread * Update proposals/NNNN-support-incremental-migration-to-concurrency-checking.md Co-authored-by: Jon Shier <[email protected]> * Assign number, kick off review Co-authored-by: Ben Cohen <[email protected]> Co-authored-by: Jon Shier <[email protected]>
hborla
referenced
this pull request
in hborla/swift-evolution
Oct 11, 2023
Use the term "disconnected" for isolation regions that are not protected by an isolation domain.
Jumhyn
added a commit
that referenced
this pull request
Jan 26, 2024
…ol`. (#2264) * Add a proposal to generalize AsyncSequence and AsyncIteratorProtocol. * Update proposals/NNNN-generalize-async-sequence.md Co-authored-by: Laszlo Teveli <[email protected]> * Update proposals/NNNN-generalize-async-sequence.md Co-authored-by: Luca Bernardi <[email protected]> * Remove generalization of isolated parameters; this is covered by a separate proposal. * Remove upfront mention of `@rethrows` in the introduction. * Generalize async sequence (#3) * Move discussion of the experimental `@rethrows` out to "Source Compatibility" * Rename `nextElement(_:)` to `next(isolation:)` * Async sequence generalization is SE-0421 --------- Co-authored-by: Laszlo Teveli <[email protected]> Co-authored-by: Luca Bernardi <[email protected]> Co-authored-by: Doug Gregor <[email protected]> Co-authored-by: Freddy Kellison-Linn <[email protected]>
slavapestov
pushed a commit
to slavapestov/swift-evolution
that referenced
this pull request
Mar 8, 2024
Remove inferred conditional copyability section
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.
The sentence I changed wasn't grammatically correct. It also used "it's" instead of "its".
This change is compatible with #2.