-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Inconsistent NamedTuple constructor behaviour #44086
Labels
kind:bug
Indicates an unexpected problem or unintended behavior
Comments
JeffBezanson
added a commit
that referenced
this issue
Feb 11, 2022
JeffBezanson
added a commit
that referenced
this issue
Feb 14, 2022
antoine-levitt
pushed a commit
to antoine-levitt/julia
that referenced
this issue
Feb 17, 2022
LilithHafner
pushed a commit
to LilithHafner/julia
that referenced
this issue
Feb 22, 2022
LilithHafner
pushed a commit
to LilithHafner/julia
that referenced
this issue
Mar 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When not specifying tuple parameters, NamedTuples extract information out of other NamedTuples correctly even when out of order
NamedTuple{(:failure,:survival,:repair)}((survival=0.5, failure=0.2, repair=0.3))
>> (failure = 0.2, survival = 0.5, repair = 0.3)
However, if I specify the tuple type, it fails to correctly re-order
NamedTuple{(:failure,:survival,:repair), NTuple{3,Float64}}((survival=0.5, failure=0.2, repair=0.3))
>> (failure = 0.5, survival = 0.2, repair = 0.3)
The text was updated successfully, but these errors were encountered: