Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix some leftover instances of the old enum syntax in the manual #1548

Merged
merged 2 commits into from
Aug 28, 2023
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/manual/syntax.md
Original file line number Diff line number Diff line change
Expand Up @@ -602,7 +602,7 @@ Here are some examples of type annotations in Nickel:
error: incompatible types
[..]

> (1 + 1 : Number) + ((`foo |> match { `foo => 1, _ => 2 }) : Number)
> (1 + 1 : Number) + (('foo |> match { `foo => 1, _ => 2 }) : Number)
vkleen marked this conversation as resolved.
Show resolved Hide resolved
3

> let x : Number = "a" in x
Expand Down
2 changes: 1 addition & 1 deletion doc/manual/typing.md
Original file line number Diff line number Diff line change
Expand Up @@ -220,7 +220,7 @@ The following type constructors are available:
```

- **Enum**: ``[| 'tag1, .., 'tagn |]``: an enumeration comprised of alternatives
`tag1`, .., `tagn`. An enumeration literal is prefixed with a backtick and
`tag1`, .., `tagn`. An enumeration literal is prefixed with a single quote and
serialized as a string. It is useful to encode finite alternatives. The
advantage over strings is that the typechecker handles them more finely: it is
able to detect incomplete matches, for example.
Expand Down
Loading