Skip to content

Fixed spelling and formatting #283

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

Merged
merged 1 commit into from
Dec 6, 2015
Merged

Fixed spelling and formatting #283

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
12 changes: 6 additions & 6 deletions docs/proposals/Accessors.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ objects::
point = point1
point0.x = x
point = point0

Note that ``point.y`` is left unchanged.

Local analysis
Expand Down Expand Up @@ -157,7 +157,7 @@ through unexpected aliases::
Note that, in either solution, you've introduced extra full-value
loads. This may be quite expensive, and it's not guaranteed to be
semantically equivalent.

Performance
~~~~~~~~~~~

Expand Down Expand Up @@ -453,7 +453,7 @@ Nor can this be fixed with a purely local analysis; consider::

class C { var array: [Int] }
let global_C = C()

func assign(inout value: Int) {
C.array = []
value = 0
Expand Down Expand Up @@ -606,7 +606,7 @@ General solutions
~~~~~~~~~~~~~~~~~

A language generally has six tools for dealing with code it considers
undesireable. Some of this terminology is taken from existing
undesirable. Some of this terminology is taken from existing
standards, others not.

* The language may nonetheless take steps to ensure that the code
Expand Down Expand Up @@ -916,7 +916,7 @@ I'm almost ready to state the core rule about formal accesses, but
first I need to build up a few more definitions.

An *abstract storage location* (ASL) is:

* a global variable declaration;

* an ``inout`` parameter declaration, along with a reference
Expand Down Expand Up @@ -1106,7 +1106,7 @@ the other FA's DSN set and (2) not from a non-overlapping subobject.
Are these conditions true?

Recall that an addressor is invoked for an l-value of the form::

base.memory

or::
Expand Down