Remove `StackOverflowError` catching, use explicit `overflows` instead

[j-mie6]

Parsley previously used a safeCall mechanism to run the internal compiler in a stack-unsafe way and revert to a stack-safe version if it threw a StackOverflowError. This is not safe: this is a fatal error, and the JVM may be left in an inconsistent state after "recovery" and on Native a stack-overflow is undefined behaviour. Both not good things to be relying on. As such the automatic recovery has been removed: if a stack-overflow occurs before parsing begins then use .overflows() on the parser that is having .parse called on it to compile it in a stack-safe way. The same goes for users who wish to be immune from any potential stack-overflows full-stop.

Thanks to @armanbilge for letting me know!

[codeclimate[bot]]

Code Climate has analyzed commit 2978ba5f and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 91.7% (0.1% change).

View more on Code Climate.

[armanbilge]

Further reading:

• https://github.com/scala/scala/commit/64603653f82082431941cb29ad317b669822f28e
• https://groups.google.com/d/topic/scala-language/eC9dqTTBYHg