refactor: change onType to match and take only one pattern and result (#22)
All checks were successful
/ test (push) Successful in 17s
All checks were successful
/ test (push) Successful in 17s
Pursuant to #12. Besides changing the name of onType to match, and only allowing one pattern and result in `match()`, this PR also arranges that in place of an onType with lots of alternating PATTERN, VALUE, PATTERN, VALUE arguments, one now exports an _array_ of `match(PATTERN, VALUE)` items. Doesn't quite fully resolve #12, because there is still the question of whether `match(...)` can be left out for a behavior that literally matches anything (current behavior), or whether `match(Passthru, behavior)` should be required for such cases. Reviewed-on: #22 Co-authored-by: Glen Whitney <glen@studioinfinity.org> Co-committed-by: Glen Whitney <glen@studioinfinity.org>
This commit is contained in:
parent
491e207fad
commit
236f46c0c0
22 changed files with 147 additions and 135 deletions
|
@ -1,9 +1,9 @@
|
|||
import {NumberT} from './NumberT.js'
|
||||
|
||||
import {onType} from '#core/helpers.js'
|
||||
import {match} from '#core/helpers.js'
|
||||
import {Returns} from '#core/Type.js'
|
||||
|
||||
export const plain = f => onType(
|
||||
export const plain = f => match(
|
||||
Array(f.length).fill(NumberT), Returns(NumberT, f))
|
||||
|
||||
// Takes a behavior returning boolean, and returns a factory
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue