Fixed misspelling
This commit is contained in:
parent
aad30e4c41
commit
fc543f73a0
|
|
@ -7,7 +7,7 @@ figuring out where moves occur and tracking those.
|
|||
## Initialization and moves
|
||||
|
||||
From a user's perspective, initialization -- giving a variable some
|
||||
value -- and moves -- transfering ownership to another place -- might
|
||||
value -- and moves -- transferring ownership to another place -- might
|
||||
seem like distinct topics. Indeed, our borrow checker error messages
|
||||
often talk about them differently. But **within the borrow checker**,
|
||||
they are not nearly as separate. Roughly speaking, the borrow checker
|
||||
|
|
|
|||
|
|
@ -204,7 +204,7 @@ OK as long as the mutation is not observable. This is achieved by two things:
|
|||
This is not an ideal setup because of the manual intervention needed, so it
|
||||
should be used sparingly and only when it is well known which queries might
|
||||
access a given result. In practice, however, stealing has not turned out to be
|
||||
much of a maintainance burden.
|
||||
much of a maintenance burden.
|
||||
|
||||
To summarize: "Steal queries" break some of the rules in a controlled way.
|
||||
There are checks in place that make sure that nothing can go silently wrong.
|
||||
|
|
|
|||
|
|
@ -147,7 +147,7 @@ are both represented with an index.)
|
|||
|
||||
For each strand, we also optionally store a *selected subgoal*. This
|
||||
is the subgoal after the turnstile (`:-`) that we are currently trying
|
||||
to prove in this strand. Initally, when a strand is first created,
|
||||
to prove in this strand. Initially, when a strand is first created,
|
||||
there is no selected subgoal.
|
||||
|
||||
[`ExClause`]: https://rust-lang.github.io/chalk/doc/chalk_engine/struct.ExClause.html
|
||||
|
|
|
|||
Loading…
Reference in New Issue