Re:JavaScript Pattern Matching Proposal
by cshepp on Wednesday April 25, 2018 @04:35PM
(#16925837)
Method-based syntax for pattern matching is easier to read and grok (IMO), but it lacks the dynamic capabilities of data-oriented syntax (in Kasai, patterns can be built/manipulated at runtime). It's interesting to compare the two approaches.
[ Parent
| on HN ]
Re:JavaScript Pattern Matching Proposal
by mpfundstein on Wednesday April 25, 2018 @05:14PM
(#16926232)
If you mean by method-based pattern matching that you evaluate a function for each 'case'. My lib can do that do:
const match = require('pmatch-js')
const _ = require('lodash')
const fizzbuzz = x => match(x)
.when(a => a % 3 == 0 && a % 5 == 0, 'fizzbuzz')
.when(a => a % 5 == 0, 'buzz')
.when(a => a % 3 == 0, 'fizz')
.otherwise(a => a)
console.log(
_.range(1, 101).map(fizzbuzz).join(' ')
)
But maybe you mean something totally different :-)EDIT: Ah I think I know what you mean. Your lib takes an array of tuples to define the patterns. Sorry for the confusion.
Re:JavaScript Pattern Matching Proposal
by dkarbayev on Wednesday April 25, 2018 @06:17PM
(#16926808)
Wow, importing the whole lodash to use just one function? There’s es6 way of getting an array with a range of numbers:
[...Array(100).keys()].map(v=>v+1)
A little bit longer but no dependencies.Although this method is pretty, I see 4 loops in this small line. a better way would be to only import the range method from lodash like so :
import _range from "lodash/range";
Re:JavaScript Pattern Matching Proposal
by mpfundstein on Thursday April 26, 2018 @01:44AM
(#16929117)
Pretty cool trick mate. Didn’t know