Open nikclayton opened 1 year ago
Thanks for this report! Now that a use case appeared for such a long and
-chain, I think I will have to increase the number of generated tuple classes and the supported chain length. If building the library from sources in an included build is fine for you, you can try to tweak this in https://github.com/h0tk3y/better-parse/blob/af4599c04f84463a4b708e7e1385217b41ae7b9e/build.gradle.kts#L65
As an alternative workaround, consider splitting the rule into several shorter ones.
Thanks -- I'll wait for a new release with a fix at the moment.
Hi -- do you have plans to bump maxTupleSize
and include that in a release any time soon?
This might be a duplicate of https://github.com/h0tk3y/better-parse/issues/29. But there's no solution in that issue, and it's almost three years old.
Using Kotlin 1.8.20, and better-parse 0.4.4, this code (which is supposed to parse an Android resource qualifier string, like
values-en-rGB-land-v28
) has a runtime error:The error is:
If the number of parsers is kept to 16 or below it works. E.g., by making the following modifications to the bottom half of the file:
then the string
values-en-rGB-land
successfully parses.