Evan Rutledge Borden
Evan Rutledge Borden
map/filter/reduce are not necessary as static elements with the details in #13
By unifying these two APIs with an interface we decrease complexity in the often common verbiage we use to affect strings and arrays. IE has/contains, count/length, etc.
Previously closure compiler ignored tuple types: ``` js /** * @param {[number, string]} foo */ ``` but in the latest build these are throwing errors. This severely limits jsDoc usage.
Is it possible to suppress this warning otherwise?
I ask because I'm aware tuples are not being checked, but I have them is some locations where checks are still needed: ``` js /** * @param {{foo: Bar, baz:...
Bummer, well it would be nice to be able to set a flag to coerce tuple syntax to a `?` in the mean time. That way existing type documentation can...
Any thoughts on when this will merge and get released?
> That means that Stack is free to run the test before the library has been built Oh that is a fun side effect. Thanks for the info!
Hmm, actually I just tried out adding `bcp47` to the build depends of `doctest` and it is still giving me intermittent failure with the same errors. It seems that is...
The difference between `m` and `n` are the only blockers I can find for using `StateT`. Is there a reason these constraints are setup this way? ``` scottyT :: (Monad...