drathier

Okey, two options then. Either elm-test decides what's printable, and outputs hex digits or similar if there's an unprintable character in a string, or the runners do the same thing....

Oh, are `fuzz` tests expanded to 100 unit tests before running?

Right, shrinking. Python Hypothesis has a `note` function which works like `print` only after the shrinking is done; otherwise it's a no-op. Maybe we could supply our own `Debug.log` function...

I have seen exponential backoff in chrome (just a few minutes ago), but seem to get a constant rate of about 5 retries per second in safari doing the same...

@bgourlie would you like to fix #26 in this PR as well?

The `length` property of strings is immutable, so caching it will only slightly reduce performance in modern browsers; it's already constant time to access. `

That's the most Helpful PR I've seen in quite a while.

Oreo now does this by default it seems, and I haven't found a way to turn it off. I've learned the english voice, so getting a swedish voice every once...

The functions that convert to upper/lower case modify more than just ascii a-z. I'm fine with either, but the combination is troublesome. Personally, I'd like to drop these 4 functions...

Apparently which lowercase characters correspond to what uppercase characters is locale-dependent, so doing the non-ascii version properly will be hard. https://stackoverflow.com/questions/12537377/in-haskell-how-can-i-uppercase-a-unicode-character-with-respect-to-current-local Also, ß is a single German lowercase character, but...