Noah

I've left some comments. Generally, it's best practice to _not_ just copy whatever JS libaries do. They use bad names and bad data structures. Think about the perspective of the...

naming is hard! `githubFlavoured` would keep the API consistent, so I would probably stick with that. Or `withExtras` or something. 👍 much better names for the quote options

- [x] Use of `Regex.regex` as a non static function (runtime error abound) (#46) - [x] Use of Core's `Array` package (#51) - [x] Functions defined in let bindings (#61)

@deadfoxygrandpa ping

This has already been moved to elm-community. Deadfoxygrandpa has been unresponsive for about a month now On Monday, May 30, 2016, Esad Hajdarevic [email protected] wrote: > @deadfoxygrandpa https://github.com/deadfoxygrandpa Please consider...

Go for it, but be sure to benchmark. See this PR for more info: https://github.com/stoeffel/elm-verify-examples/pull/9

@tkreis Bring it up on Slack in #testing, and I can help out with what you need

👍

This is reasonable. I might look into it at some point in the near future if someone else hasn't already.

@mgold, tests failing can be slow. It's best to decide a cutoff point and deal with it there. E.g 3 failures then fail the test overall and stop running any...