Skip to content

Fixed typos in docs/CallingConvention.rst #71

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

Fixed typos in docs/CallingConvention.rst #71

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
6 changes: 3 additions & 3 deletions docs/CallingConvention.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ components, each operating on a different abstraction level:

* the high-level semantics of the call (pass-by-reference
vs. pass-by-value),

* the ownership and validity conventions about argument and result
values ("+0" vs. "+1", etc.), and

Expand Down Expand Up @@ -280,7 +280,7 @@ considering here:
for the value, this convention allows the callee to use the value at
a later point without taking any extra action to keep it alive.

The flipside is that this convention requires a lot of extra work
The flip side is that this convention requires a lot of extra work
when a single value is used multiple times in the caller. For
example, a value passed in every iteration of a loop will need to be
copied/retained/whatever each time.
Expand Down Expand Up @@ -1181,7 +1181,7 @@ legal type sequences from the direct results. If this yields an empty
sequence, the result type is `void`. If it yields a single legal
type, the result type is the corresponding Clang type. No other could
actually have come from an imported C declaration, so we don't have
any real compatiblity requirements; for the convenience of
any real compatibility requirements; for the convenience of
interoperation, this is handled by constructing a new C struct which
contains the corresponding Clang types for the legal type sequence as
its fields.
Expand Down