Repository navigation
Fix Monad instance for PolygonalSummaryResult - #3221
Merged
echeipesh merged 2 commits intoApr 7, 2020
Merged
Conversation
Avoids StackOverflow through unterminated self-recursion
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes the implementation of the Monad instance to avoid self-recursion
Problem
Fixed
Note that the
Summaryinstance has to be upcast toPolygonalSummaryResultin order for the providedMonadinstance to be discovered. This looks weird in console but in practice its not much of an issue because the point of this ADT is that you don't know if the result will beSummaryorNoIntersection. That is all polygonal summary functions actually have return type ofPoloygonalSummaryResult[A]