You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The second part of this came up in discussion with @TIHan about the potential need to write and discuss RFCs for features like RFC FS-1060 (nullable reference types) and RFC FS1071 (witness passing) and RFC FS- 1043 (extension methods visible to trait constraints). RFC FS-1060 for example adds a second optional stream of F# metadata for nullability annotations. We may well want to generalise this mechanism in the future to allow additional layering of information that refines and augments the existing information in the metadata format
SO note that a detailed technical spec is not the critical thing, but more a spec that discusses the properties we expect of the metadata format and its consuming/producing tooling, and how this also relates to key assemblies like FSharp.Core.
This discussion was converted from issue #484 on December 21, 2020 20:11.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We should add a specs folder
The F# Language spec (when we eventually convert it to markdown)
The F# compiler metadata format spec (i.e. the format read/written by
TypedTreePickle.fs
) and the corresponding [optimization info] (https://github.com/dotnet/fsharp/blob/master/src/fsharp/Optimizer.fsi), including its versioning properties/policyThe second part of this came up in discussion with @TIHan about the potential need to write and discuss RFCs for features like RFC FS-1060 (nullable reference types) and RFC FS1071 (witness passing) and RFC FS- 1043 (extension methods visible to trait constraints). RFC FS-1060 for example adds a second optional stream of F# metadata for nullability annotations. We may well want to generalise this mechanism in the future to allow additional layering of information that refines and augments the existing information in the metadata format
SO note that a detailed technical spec is not the critical thing, but more a spec that discusses the properties we expect of the metadata format and its consuming/producing tooling, and how this also relates to key assemblies like FSharp.Core.
Beta Was this translation helpful? Give feedback.
All reactions