Repository navigation
Allow mixing ranges and values in collection expressions #20759
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
Open
xperiandri
wants to merge
6
commits into
dotnet:main
Choose a base branch
from
xperiandri:feature/fs-1031-mixed-ranges
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+536
−38
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
5c40f03
Allow mixing ranges and values in collection expressions
xperiandri 9fbaaab
Add release notes for mixed ranges and values
xperiandri d7d9177
Report only FS3925 for a range that is yielded or returned
xperiandri 3f61cc2
Fold the mixed range fixture files into named scenarios
xperiandri 7cf83f1
Shrink the mixed range change and fix the range lowering it exposed
xperiandri c89137e
Add compiler benchmarks for mixed ranges, explicit yield! and flat li…
xperiandri File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖🕵️⏱️🔥
Add mixed-range, explicit-
yield!, and flat-value compiler benchmarks before merge. The bounded 5k computed forms exceeded 180s while flat values stayed ~0.8s; track the scaling instead of relying on correctness-only tests.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added in a4bd607:
MixedRangeBenchmarksin the compiler benchmarks. Each benchmark checks a list ofCountelements forCount250, 500 and 1000: the flat literal is the baseline, the other two are mixed ranges and the explicityield!form, with a range at every tenth element. Local Release build,--inProcess:yield!The flat literal stays constant. Mixed ranges and explicit
yield!grow about 4x per doubling, and so do their allocations (105, 196, 543 MB against a flat 70 MB), and mixed is never slower than explicit: both are checked by the sequence-expression checker. So the PR adds no new cliff, but the cost of these forms is not linear. The SDK compiler already overflows its stack on the explicit form at 1,500 elements, while the flat literal is fine. I did not change the checker's complexity here.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow-up after the rebase onto main (the benchmark commit is c89137e now, not a4bd607). On current main the stack guard from #20480 keeps the explicit and the mixed form from crashing, but they are slow instead: the
Typecheckphase takes 5 s for 2000yieldstatements and 40 to 60 s for 3000, against 1.5 s for the flat literal at any size, and much more when the machine is busy, so the more than 180 s you saw at 5k fits. I am filing an issue for the checker, and I suggested a softer Scaling sentence in fsharp/fslang-design#860 (the RFC says checking MUST stay linear).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue for the checker is #20887.