Skip to content

[fix]: minor typo cleanup in Swift 5 exclusivity article #1258

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.

Sign up for GitHub

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

Open
jamieQ wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[fix]: minor typo cleanup in Swift 5 exclusivity article #1258

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions _posts/2019-02-05-swift-5-exclusivity.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -280,9 +280,9 @@ considered a violation of exclusivity when two separate properties are
written and read; `point.x` and `point.y`. Because `Point` is declared
as a `struct`, it is considered a value type, meaning that all of its
properties are part of a whole value, and accessing one property
accesses the entire value. The compiler makes exception to this rule
accesses the entire value. The compiler makes an exception to this rule
when it can prove safety via a straighforward static analysis. In
particular, when same statement initiates accesses of two disjoint
particular, when the same statement initiates accesses of two disjoint
stored properties, the compiler avoids reporting an exclusivity
violation. In the next example, the statement that calls `modifyX`
first accesses `point` in order to immediately pass its property `x`
Expand Down