Split overcomplicated sentence into two
This commit is contained in:
parent
e5017443f2
commit
a6843376d8
|
|
@ -64,8 +64,8 @@ There are essentially four kinds of representations one might want of a value:
|
||||||
* `Operand` is an argument to e.g. a `+` operation or a function call
|
* `Operand` is an argument to e.g. a `+` operation or a function call
|
||||||
* a temporary variable containing a copy of the value
|
* a temporary variable containing a copy of the value
|
||||||
|
|
||||||
Since we start out with lowering the function body to an `Rvalue` so we can create an
|
We start out with lowering the function body to an `Rvalue` so we can create an
|
||||||
assignment to `RETURN_PLACE`, that `Rvalue` lowering will in turn trigger lowering to
|
assignment to `RETURN_PLACE`, This `Rvalue` lowering will in turn trigger lowering to
|
||||||
`Operand` for its arguments (if any). `Operand` lowering either produces a `const`
|
`Operand` for its arguments (if any). `Operand` lowering either produces a `const`
|
||||||
operand, or moves/copies out of a `Place`, thus triggering a `Place` lowering. An
|
operand, or moves/copies out of a `Place`, thus triggering a `Place` lowering. An
|
||||||
expression being lowered to a `Place` can in turn trigger a temporary to be created
|
expression being lowered to a `Place` can in turn trigger a temporary to be created
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue