-
Notifications
You must be signed in to change notification settings - Fork 809
Issues: dotnet/fsharp
Celebrating the F# 9 Release: A Tribute to Our Contributors
#17996
opened Nov 13, 2024 by
vzarytovskii
Open
1
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Visual Studio constantly hangs for multitarget project - stacks point to F# code.
Area-VS
VS support for F# not covered elsewhere
Bug
Impact-High
(Internal MS Team use only) Describes an issue with extreme impact on existing code.
Nullness issue - Regression in member constraint overload resolution with Issues related to handling of Nullable Reference Types
Bug
Impact-Medium
(Internal MS Team use only) Describes an issue with moderate impact on existing code.
null
-constrained methods from pre-F# 9-compiled code
Area-Nullness
Namespace open is incorrectly reported as redundant
Area-LangService-CodeFixes
Code fixes associated with diagnostics
Bug
Impact-Low
(Internal MS Team use only) Describes an issue with limited impact on existing code.
Struct optional parameter with caller info attributes will fails in type check
Area-Compiler-Checking
Type checking, attributes and all aspects of logic checking
Bug
Impact-Medium
(Internal MS Team use only) Describes an issue with moderate impact on existing code.
RuntimeWrappedException cannot be caught
Area-Compiler-CodeGen
IlxGen, ilwrite and things at the backend
Bug
Impact-Low
(Internal MS Team use only) Describes an issue with limited impact on existing code.
Field in a record named the same as a DUs case inside of module of the same name of the record type fails to pattern match
Area-Compiler-Checking
Type checking, attributes and all aspects of logic checking
Bug
Impact-Low
(Internal MS Team use only) Describes an issue with limited impact on existing code.
Nullness issue - Can't cleanly implement INotifyPropertyChanged by publishing an Event
Area-Nullness
Issues related to handling of Nullable Reference Types
Bug
#r "nuget: .." in VisualFSI produces an interesting warning
Area-VS-FSI
VS window and commands for F# Interactive
Bug
Impact-Low
(Internal MS Team use only) Describes an issue with limited impact on existing code.
Nullness issue – Publishing an event produces nullness warning
Area-Nullness
Issues related to handling of Nullable Reference Types
Bug
Impact-Low
(Internal MS Team use only) Describes an issue with limited impact on existing code.
Backwards compatibility broken
Area-Compiler-SRTP
bugs in SRTP inference, resolution, witness passing, code gen
Bug
Impact-High
(Internal MS Team use only) Describes an issue with extreme impact on existing code.
Nullness issue – Invalid type constraint resolution on Issues related to handling of Nullable Reference Types
Bug
Impact-Medium
(Internal MS Team use only) Describes an issue with moderate impact on existing code.
ILookup
Area-Nullness
CI should check the dev container setup
Area-Tooling
Generic tooling bugs and suggestions, which do not fall into any existing category.
Continuous Improvement
help wanted
Using a non-null constant expression bound to a literal variable of a less-specific type generates invalid IL
Area-Compiler-CodeGen
IlxGen, ilwrite and things at the backend
Bug
Impact-Medium
(Internal MS Team use only) Describes an issue with moderate impact on existing code.
"as" pattern with an identifier picks a literal
Area-Compiler-PatternMatching
pattern compilation, active patterns, performance, codegen
Bug
Impact-Medium
(Internal MS Team use only) Describes an issue with moderate impact on existing code.
Needs-design
Cannot assign to byref-returning type functions
Area-Compiler-Checking
Type checking, attributes and all aspects of logic checking
Bug
Impact-Low
(Internal MS Team use only) Describes an issue with limited impact on existing code.
Unexpected warning Type checking, attributes and all aspects of logic checking
Bug
Impact-Medium
(Internal MS Team use only) Describes an issue with moderate impact on existing code.
The default value does not have the same type as the argument
Area-Compiler-Checking
Visual Studio Debugger error dialog: "To prevent an unsafe abort when evaluating the function *.__DebugDisplay" all threads where allowed to run.
Area-Debug
stepping, debug points, stacks and more
Bug
Impact-High
(Internal MS Team use only) Describes an issue with extreme impact on existing code.
Previous Next
ProTip!
no:milestone will show everything without a milestone.