Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: make sure runEither isn't calling itself #107

Merged
merged 1 commit into from
Jan 26, 2024

Conversation

ckipp01
Copy link
Contributor

@ckipp01 ckipp01 commented Jan 26, 2024

It looks like this was overlooked and the overloaded runEither is just constantly calling itself resulting in a stack overflow. This changes it to call the newly created runEither with the nameMapper which I believe is the intended flow.

fixes #106

It looks like this was overlooked and the overloaded `runEither` is just
constantly calling itself resulting in a stack overflow. This changes it
to call the newly created `runEither` with the `nameMapper` which I
believe is the intended flow.

fixes com-lihaoyi#106
@lihaoyi
Copy link
Member

lihaoyi commented Jan 26, 2024

Thanks @ckipp01 ! Will cut a new release

@lihaoyi lihaoyi merged commit ee61f5e into com-lihaoyi:main Jan 26, 2024
4 checks passed
@lefou lefou added this to the 0.6.1 milestone Jan 26, 2024
@ckipp01 ckipp01 deleted the recursionGoneWrong branch January 26, 2024 10:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Minimal example now results in a StackOverflowError as of 0.6.0
3 participants