Skip to content

Commit d6c5b78

Browse files
committed
Temporarily remove broken links
1 parent 48f62e4 commit d6c5b78

File tree

2 files changed

+3
-5
lines changed

2 files changed

+3
-5
lines changed

book/src/engine/logic.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ As either `Answer`s are found for the selected `Table`, entries on the stack are
3434

3535
As mentioned before, whenever a new `Goal` is encounted, a new [`Table`] is
3636
created to store current and future answers. First, the [`Goal`] is converted into
37-
an [`HhGoal`]. If it can be simplified, then a `Strand` with one or more
37+
an `HhGoal`. If it can be simplified, then a `Strand` with one or more
3838
subgoals will be generated and can be followed as above. Otherwise, if it is a
3939
`DomainGoal` (see above), then
4040
[`program_clauses`](https://rust-lang.github.io/chalk/chalk_engine/context/trait.ContextOps.html#tymethod.program_clauses)
@@ -123,7 +123,6 @@ For much more in-depth
123123

124124
[`Strand`]: https://rust-lang.github.io/chalk/chalk_engine/strand/struct.Strand.html
125125
[`Context`]: https://rust-lang.github.io/chalk/chalk_engine/context/trait.Context.html
126-
[`HhGoal`]: https://rust-lang.github.io/chalk/chalk_engine/hh/enum.HhGoal.html
127126
[`Stack`]: https://rust-lang.github.io/chalk/chalk_engine/stack/struct.Stack.html
128127
[`StackEntry`]: https://rust-lang.github.io/chalk/chalk_engine/stack/struct.StackEntry.html
129128
[`Table`]: https://rust-lang.github.io/chalk/chalk_engine/table/struct.Table.html

book/src/engine/major_concepts.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ opaque to the engine internals. Functions in the trait are agnostic to specific
1616
program or environment details, since they lack a `&self` argument.
1717

1818
To give an example, there is an associated [`Goal`] type. However, Chalk doesn't
19-
know how to solve this. Instead, it has to be converted an [`HhGoal`] via the
19+
know how to solve this. Instead, it has to be converted an `HhGoal` via the
2020
`Context::into_hh_goal` function. This will be coverted more in the `Goals`
2121
section.
2222

@@ -38,7 +38,7 @@ change the state of the logic itself.
3838
## Goals
3939

4040
A "goal" in Chalk can be thought of as "something we want to prove". The engine
41-
itself understands [`HhGoal`]s. `HHGoal`s consist of the most basic logic,
41+
itself understands `HhGoal`s. `HHGoal`s consist of the most basic logic,
4242
such as introducing Binders (`Forall` or `Exists`) or combining goals (`All`).
4343
On the other hand, `Context::Goal` represents an opaque goal generated
4444
externally. As such, it may contain any extra information or may be interned.
@@ -111,7 +111,6 @@ stack).
111111
[`Context`]: https://rust-lang.github.io/chalk/chalk_engine/context/trait.Context.html
112112
[`ContextOps`]: https://rust-lang.github.io/chalk/chalk_engine/context/trait.ContextOps.html
113113
[`InferenceTable`]: https://rust-lang.github.io/chalk/chalk_engine/context/trait.InferenceTable.html
114-
[`HhGoal`]: https://rust-lang.github.io/chalk/chalk_engine/hh/enum.HhGoal.html
115114
[`Solution`]: https://rust-lang.github.io/chalk/chalk_engine/context/trait.Context.html#associatedtype.Solution
116115
[`ExClause`]: https://rust-lang.github.io/chalk/chalk_engine/struct.ExClause.html
117116
[`Strand`]: https://rust-lang.github.io/chalk/chalk_engine/strand/struct.Strand.html

0 commit comments

Comments
 (0)