Skip to content

Commit 0171e75

Browse files
authored
Merge pull request #35257 from apple/gottesmm-patch-1-sil.rst
[sil.rst] Fix some formatting
2 parents 750d559 + f5e34b3 commit 0171e75

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/SIL.rst

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1787,15 +1787,15 @@ the ``ValueOwnershipKind`` of ``v``. In symbols, we must have that::
17871787

17881788
In words, a value can be passed to an operand if applying the operand's
17891789
ownership constraint to the value's ownership does not change the value's
1790-
ownership. Operationally this has a few interesting effects on SIL::
1790+
ownership. Operationally this has a few interesting effects on SIL:
17911791

1792-
1. We have defined away invalid value-operand (aka def-use) pairing since the
1793-
SILVerifier validates the aforementioned relationship on all SIL values,
1794-
uses at all points of the pipeline until ossa is lowered.
1792+
1. We have defined away invalid value-operand (aka def-use) pairing since the
1793+
SILVerifier validates the aforementioned relationship on all SIL values,
1794+
uses at all points of the pipeline until ossa is lowered.
17951795

1796-
2. Many SIL instructions do not care about the ownership kind that their value
1797-
will take. They can just define all of their operand's as having an
1798-
ownership constraint of Any.
1796+
2. Many SIL instructions do not care about the ownership kind that their value
1797+
will take. They can just define all of their operand's as having an
1798+
ownership constraint of Any.
17991799

18001800
Now lets go into more depth upon `Value Ownership Kind`_ and `Ownership Constraint`_.
18011801

0 commit comments

Comments
 (0)