Skip to content

Commit

Permalink
user_manual: fixing semantics of :implicit annotation
Browse files Browse the repository at this point in the history
  • Loading branch information
Mallku2 committed Feb 18, 2025
1 parent 917867f commit b19b73c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion user_manual.md
Original file line number Diff line number Diff line change
Expand Up @@ -236,7 +236,7 @@ In contrast, the example below declares a predicate `=` where the type of the ar
(define P ((x Int) (y Int)) (= x y))
```

In general, a type argument can be made implicit if its value can be inferred from the type of later arguments.
In general, an argument can be made implicit if its value can be inferred from the type of later arguments.

We call `T` in the above definitions a _parameter_. The free parameters of the return type of an expression should be contained in at least one non-implicit argument. In particular, the following declaration is malformed, since the return type of `f` cannot be inferred from its arguments:

Expand Down

0 comments on commit b19b73c

Please sign in to comment.