Make shortest-path functions safer. #64
Merged
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.
Namely:
return
Nothing
instead of failing with the dreaded*** Exception: Prelude.head: empty list
(forspLength
) or returningnon-sense (for
sp
) when the source is not connected to thedestination.
mention in the docs that negative edge weights will not produce the
right answer.
add tests that check that
Nothing
andJust
are returned whenthey should be for shortest-path operations.
I just used your great library for the first time but wasted time with
Prelude.head: empty list
fromspLength
. This patch will avoid that problem for future users.