Skip to content

Fix typos #76

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 #76

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/CallingConvention.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ Pass-by-value

In pass-by-value, if `A` is an l-value expression, `foo(A)` copies the
current value there. Any modifications `foo` makes to its parameter
are make to this copy, not to the original l-value.
are made to this copy, not to the original l-value.

Most modern languages are pass-by-value, with specific functions able
to opt in to pass-by-reference semantics. This is exactly what Swift
Expand Down Expand Up @@ -345,7 +345,7 @@ just add default arguments at each step) have really awful performance
because the compiler is adding retains and releases at every single
level. It's just not a good convention to adopt by default. However,
we might want to consider allowing specific function parameters to opt
into it; sort comparators are an particularly interesting candidate
into it; sort comparators are a particularly interesting candidate
for this. `unowned` is very similar to C++'s `const &` for things
like that.

Expand Down