Make ``ParsingException`` a ``RuntimeException``

[litetex]

Currently ParsingException is a normal checked Exception that needs to be explicitly declared everywhere, where it might be thrown or used.

This is kind of problematic when working with Java's streaming API or other reactive patterns because you can't use checked exceptions there.

Therefore it would be a lot better to make ParsingException extend RuntimeException instead.

[absurdlylongusername]

I agree with this. Considering that regex exceptions are also runtime exceptions (and we often throw ParsingException in regex scenarios), it falls into the same category

[Stypox]

Mmmh but then you would lose Java's requirement/guarantee to put throws ... annotations on methods, and we would therefore be more likely to forget that a method is fallible, because RuntimeExceptions do not need to be specified. However Kotlin removed this requirement anyway, so I agree with this.

[absurdlylongusername]

I think it would be better to just convert the extractor to Kotlin. Although making it runtime would be a good temporary measure, having extractor in Kotlin would solve a lot of problems at the same time