fix: fix parsing in Elixir 1.20 - #20
Merged
Merged
Conversation
dmuharemagic
approved these changes
Jun 30, 2026
Confirmed, works |
Contributor
|
Looks good. Thank you for the contribution! |
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
3 participants
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 fix is similar to the one required for Elixir 1.16 #15.
This problem manifests only during a mismatch of the left and right side and when the asserting value is complex enough. Not sure what "complex enough" means, but simple map assert (
assert_value(%{a: 1} == %{}) works, but large, nested map does not work.