-
Notifications
You must be signed in to change notification settings - Fork 823
Allow typed bindings(and!) in CE without parentheses #18682
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
Draft
edgarfgp
wants to merge
34
commits into
dotnet:main
Choose a base branch
from
edgarfgp:allow-and-bang-typed-bindings
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.
+2,056
−14
Draft
Changes from all commits
Commits
Show all changes
34 commits
Select commit
Hold shift + click to select a range
1799aaf
make attribute targets mismatches a warning and not an error.
edgarfgp 55507e9
release notes
edgarfgp 1738018
update tests
edgarfgp 65f5bb6
Merge branch 'main' into fix-attr-targets
edgarfgp 0c97b9d
Merge branch 'main' into fix-attr-targets
edgarfgp 6f2b706
update baselines
edgarfgp e8f1bb0
Merge branch 'main' into fix-attr-targets
edgarfgp 75d8f5e
Update baselines
edgarfgp 4f2e97e
Merge branch 'fix-attr-targets' of github.com:edgarfgp/fsharp into fi…
edgarfgp 63be5d5
Merge branch 'main' into fix-attr-targets
edgarfgp 4248f2a
Move attribute form logic to an AP
edgarfgp cc96217
Merge branch 'main' into fix-attr-targets
edgarfgp e270b88
Merge branch 'main' into fix-attr-targets
edgarfgp e0cc65a
Merge branch 'main' into fix-attr-targets
edgarfgp 1e29d58
Merge branch 'main' into fix-attr-targets
edgarfgp 1470bf9
Merge branch 'main' into fix-attr-targets
edgarfgp 8988215
Merge branch 'main' into fix-attr-targets
edgarfgp 74712e8
Merge branch 'main' into fix-attr-targets
edgarfgp 967c4a9
Merge branch 'main' of github.com:edgarfgp/fsharp
edgarfgp a30cef4
Merge branch 'dotnet:main' into main
edgarfgp 5fa0480
Merge branch 'dotnet:main' into main
edgarfgp 15e3d34
Merge branch 'dotnet:main' into main
edgarfgp b7ffcf8
Merge branch 'dotnet:main' into main
edgarfgp 549f961
Add new parser rule and syntax tree tests
edgarfgp b3f4baa
Add CE test that uses let! and and!
edgarfgp 98937bc
more syntax tree tests
edgarfgp a020505
more syntax tree tests
edgarfgp 1ba22bf
Merge branch 'main' into allow-and-bang-typed-bindings
edgarfgp dce81de
more syntax tree tests
edgarfgp c921606
Merge branch 'allow-and-bang-typed-bindings' of github.com:edgarfgp/f…
edgarfgp 86fedfd
Update LanguageFeature and release notes
edgarfgp aee26ec
update baselines
edgarfgp 4712569
more tests
edgarfgp 43a4c21
Merge branch 'main' into allow-and-bang-typed-bindings
edgarfgp 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
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.
At this point we should probably try to unify
let
andlet!
parsing rules and check whether it's a!
version or not in the type checker. As the first step it should be at least parse it in a unified manner and then create different tree nodes conditionally. But ideally it should be something likeisComputed: bool
flag that the type checker would inspect.@edgarfgp Do you think it's feasible to unify the rules as part of this PR?
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.
Agreed. I think as part of this PR I can try and I can try and unify the parsing rules for
let
,let!
andand!
.Yeah I can add syntax tree test that show the parsing errors.
cc @T-Gro any objections ?