Skip to content

Fix Typos and spelling #41

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 3, 2015
Merged

Fix Typos and spelling #41

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 docs/HighLevelSILOptimizations.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,7 +167,7 @@ array.props.isCocoa/needsElementTypeCheck -> Bool
Reads storage descriptors properties (isCocoa, needsElementTypeCheck).
This is not control dependent or guarded. The optimizer has
semantic knowledge of the state transfer those properties can not make:
An array that is not ``isCocoa`` can not tranfer to ``isCocoa``.
An array that is not ``isCocoa`` can not transfer to ``isCocoa``.
An array that is not ``needsElementTypeCheck`` can not transfer to
``needsElementTypeCheck``.

Expand Down Expand Up @@ -228,7 +228,7 @@ array.mutate_unknown
dependent. ``mutate_unknown`` also implies the guarding semantics of
``make_mutable``. It is not itself guarded by ``make_mutable`` and
may act as a guard to other mutating operations, such as
``get_element_address``. Combining semantics allows the flexbility in how
``get_element_address``. Combining semantics allows the flexibility in how
the array copy is implemented in conjunction with implementing
mutating functionality. This may be more efficient than cleanly
isolating the copy and mutation code.
Expand Down