Improve Parse.Ref

[marcin-golebiowski]

It looks like Parse.Ref is having some problems when used heavily together with Or.
Please take a look at my fix, a unit test.

There is also workaround but I would prefer not to use it.
The workaround:

• Change Parse.Ref(() => parser) to Parse.Ref(() => parser.Named("unique_name"))

Best regards,
Marcin

[nblumhardt]

Thanks for the PR, Marcin 👍

Seems like a bug/design limitation of memos, though not having been in the codebase for a while, I can't immediately spot it... happy to push forward with the fix as-is, but if you (or anyone following along) can spot the underlying issue, it'd be great to be able to address it at a lower level 🤔

[marcin-golebiowski]

I will try to create additional unit tests later today to check if the fix doesn't break anything.

[marcin-golebiowski]

@nblumhardt Please find my latest changes.

I think the latest commit contains proper solution to the problem.
I think it's better than my original one.
The initial and second solution solves #166

Best regards,
Marcin

[nblumhardt]

Awesome! Thank you, Marcin 👍