2024-03-18 19:01:43 +03:00
|
|
|
Some tests of pattern behavior.
|
|
|
|
|
2024-07-10 17:46:18 +03:00
|
|
|
``` unison
|
2024-03-18 19:01:43 +03:00
|
|
|
p1 = join [literal "blue", literal "frog"]
|
|
|
|
|
|
|
|
> Pattern.run (many p1) "bluefrogbluegoat"
|
2024-03-29 19:39:30 +03:00
|
|
|
> Pattern.run (many.corrected p1) "bluefrogbluegoat"
|
2024-03-18 19:01:43 +03:00
|
|
|
```
|
|
|
|
|
2024-07-10 19:17:15 +03:00
|
|
|
``` ucm
|
2024-03-18 19:01:43 +03:00
|
|
|
|
|
|
|
Loading changes detected in scratch.u.
|
|
|
|
|
|
|
|
I found and typechecked these definitions in scratch.u. If you
|
|
|
|
do an `add` or `update`, here's how your codebase would
|
|
|
|
change:
|
|
|
|
|
|
|
|
⍟ These new definitions are ok to `add`:
|
|
|
|
|
|
|
|
p1 : Pattern Text
|
|
|
|
|
|
|
|
Now evaluating any watch expressions (lines starting with
|
|
|
|
`>`)... Ctrl+C cancels.
|
|
|
|
|
|
|
|
3 | > Pattern.run (many p1) "bluefrogbluegoat"
|
2024-03-29 19:39:30 +03:00
|
|
|
⧩
|
|
|
|
Some ([], "goat")
|
|
|
|
|
|
|
|
4 | > Pattern.run (many.corrected p1) "bluefrogbluegoat"
|
2024-03-18 19:01:43 +03:00
|
|
|
⧩
|
|
|
|
Some ([], "bluegoat")
|
|
|
|
|
|
|
|
```
|