Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fix anonymous records internal error when nested with overlapping labels#15519

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

abonie
Copy link
Member

@abonieabonie commentedJun 28, 2023
edited
Loading

This will fix secondary issue reported here#6411

AnonRecdTypeInfo was concatenating all of the record's sorted labels to create a key for some post inference check. If for two records concatenating their labels gave the same result, then the key was also the same which resulted in some collisions.

@abonieabonie marked this pull request as ready for reviewJune 30, 2023 10:59
@abonieabonie requested a review froma team as acode ownerJune 30, 2023 10:59
Copy link
Member

@psfinakipsfinaki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Nice one

T-Gro
T-Gro previously requested changesJun 30, 2023
Copy link
Member

@T-GroT-Gro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Postponing until we get a clarification/test/.. on how this affects name stability.

The RFC explicitely mentions also here:
This name must never change in future F# compilers

@abonieabonie marked this pull request as draftJune 30, 2023 15:17
@abonieabonieforce-pushed thefix-anonrecd-nested-with-label-overlap branch from751ec73 to4b4e365CompareJuly 4, 2023 15:34
@abonieabonie marked this pull request as ready for reviewJuly 11, 2023 14:56
@abonieabonie requested review fromT-Gro andpsfinakiJuly 11, 2023 14:56
@abonie
Copy link
MemberAuthor

Postponing until we get a clarification/test/.. on how this affects name stability.

The RFC explicitely mentions also here:This name must never change in future F# compilers

I have addressed this now. It's a bit clunky - we use new modified stamps everywhere except for generating type names, where we use the old recipe - just to make sure it does not affect backward compatibility.

Copy link
Contributor

@KevinRansomKevinRansom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Looks great.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@KevinRansomKevinRansomKevinRansom approved these changes

@T-GroT-GroAwaiting requested review from T-Gro

@psfinakipsfinakiAwaiting requested review from psfinaki

Assignees
No one assigned
Labels
None yet
Projects
Archived in project
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@abonie@KevinRansom@psfinaki@T-Gro

[8]ページ先頭

©2009-2025 Movatter.jp