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

erl_types: Fix map type parsing bug (ERL-177) #1115

Merged
merged 1 commit into from
Jun 30, 2016

Conversation

margnus1
Copy link
Contributor

@margnus1 margnus1 commented Jun 28, 2016

t_map/3 previously required callers to perform normalisation of
X:=none() pairs, but as t_from_form/5 would sometimes fail to do so,
this requirement is relaxed.

This caused a dialyzer crash when using remote types as values of
mandatory pairs with singleton keys.

Bug (ERL-177) reported and shrunk by Luke Imhoff.

This PR was previously #1114, but was rebased from maint to maint-19.

t_map/3 previously required callers to perform this normalisation, but
as t_from_form/5 would sometimes fail to do so, this requirement is
relaxed.

Bug (ERL-177) reported and shrunk by Luke Imhoff.
@margnus1 margnus1 changed the title erl_types: Normalise X:=none() pairs in t_map/3 erl_types: Fix map type parsing bug (ERL-177) Jun 28, 2016
@uabboli uabboli self-assigned this Jun 28, 2016
@KronicDeth
Copy link
Contributor

Linking handle into this issue, @KronicDeth = Luke Imhoff

@OTP-Maintainer
Copy link

Patch has passed first testings and has been assigned to be reviewed


I am a script, I am not human


@HansN HansN merged commit a296fc4 into erlang:maint-19 Jun 30, 2016
@margnus1 margnus1 deleted the map-mand-remote branch June 30, 2016 10:20
@KronicDeth
Copy link
Contributor

Thanks for the PR @margnus1. How do PRs merged to a maint-<major> work? Does it mean this will be released in 19.1 or will there be a bug fix release of 19, 19.0.1? I primarily care about how it will be available in esl-erlang and then homebrew for OSX.

@margnus1
Copy link
Contributor Author

@KronicDeth Looking at the top commit in maint-19, it seems that it will end up in 19.0.1 in addition to 19.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants