More release note entries

docs/release-notes/.FSharp.Compiler.Service/8.0.200.md

@@ -2,8 +2,14 @@
 
 * Miscellaneous fixes to parentheses analysis. ([PR #16262](https://github.com/dotnet/fsharp/pull/16262), [PR #16391](https://github.com/dotnet/fsharp/pull/16391), [PR #16370](https://github.com/dotnet/fsharp/pull/16370), [PR #16395](https://github.com/dotnet/fsharp/pull/16395))
 * Correctly handle assembly imports with public key token of 0 length. ([Issue #16359](https://github.com/dotnet/fsharp/issues/16359), [PR #16363](https://github.com/dotnet/fsharp/pull/16363))
-* Fix #16398 - The dotnet framework has a limit of ~64K methods in a single class.  Introduce a compile-time error if any class has over approx 64K methods in generated IL
+* Range of [SynField](../reference/fsharp-compiler-syntax-synfield.html) ([PR #16357](https://github.com/dotnet/fsharp/pull/16357))
+* Limit a type to 65K methods, introduce a compile-time error if any class has over approx 64K methods in generated IL. ([Issue #16398](https://github.com/dotnet/fsharp/issues/16398), [#PR 16427](https://github.com/dotnet/fsharp/pull/16427))
 
 ### Added
 * Raise a new error when interfaces with auto properties are implemented on constructor-less types. ([PR #16352](https://github.com/dotnet/fsharp/pull/16352))
 * Allow usage of `[<TailCall>]` with older `FSharp.Core` package versions. ([PR #16373](https://github.com/dotnet/fsharp/pull/16373))
+* Parser recovers on unfinished `as` patterns. ([PR #16404](https://github.com/dotnet/fsharp/pull/16404))
+* Allow type-checking of unfinished object expressions. ([PR #16413](https://github.com/dotnet/fsharp/pull/16413))
+* Parser recovers on unfinished enum case declarations. ([PR #16401](https://github.com/dotnet/fsharp/pull/16401))
+* Parser recovers on unfinished record declarations. ([PR #16357](https://github.com/dotnet/fsharp/pull/16357))
+* `MutableKeyword` to [SynFieldTrivia](../reference/fsharp-compiler-syntaxtrivia-synfieldtrivia.html) ([PR #16357](https://github.com/dotnet/fsharp/pull/16357))

docs/release-notes/.Language/preview.md

@@ -1,4 +1,9 @@
 ### Added
 
 * Better generic unmanaged structs handling. ([Language suggestion #692](https://github.com/fsharp/fslang-suggestions/issues/692), [PR #12154](https://github.com/dotnet/fsharp/pull/12154))
-* Bidirectional F#/C# interop for 'unmanaged' constraint. ([PR #12154](https://github.com/dotnet/fsharp/pull/12154))
+* Bidirectional F#/C# interop for 'unmanaged' constraint. ([PR #12154](https://github.com/dotnet/fsharp/pull/12154))
+* Make `.Is*` discriminated union properties visible. ([Language suggestion #222](https://github.com/fsharp/fslang-suggestions/issues/222), [PR #16341](https://github.com/dotnet/fsharp/pull/16341))
+
+### Fixed
+
+* Allow extension methods without type attribute work for types from imported assemblies. ([PR #16368](https://github.com/dotnet/fsharp/pull/16368))

docs/release-notes/.aux/Common.fsx

@@ -1,4 +1,5 @@
-#r "nuget: Markdig, 0.33.0"
+#i "nuget: https://api.nuget.org/v3/index.json"
+#r "nuget: Markdig, 0.33.0"
 #r "nuget: FsHttp, 12.1.0"
 
 open System.IO

docs/running-documentation-locally.md

@@ -0,0 +1,46 @@
+---
+title: Running the documentation locally
+category: Compiler Internals
+categoryindex: 200
+index: 999
+---
+# Running the documentation locally
+
+The source of this documentation website is hosted on https://github.com/fsharp/fsharp-compiler-docs.  
+You can follow this guide to see the results of your document changes rendered in the browser.
+
+## Setup
+
+`fsharp/fsharp-compiler-docs` will clone the `dotnet/fsharp` repository first to generate the documentation.  
+You can however, easily run the documentation locally and modify the `docs` from `dotnet/fsharp`.
+
+* Clone `fsharp/fsharp-compiler-docs` at the same level as your local `dotnet/fsharp` repository:
+
+
+    git clone https://github.com/fsharp/fsharp-compiler-docs.git
+
+
+* Restore the `FSharp.Compiler.Service` project in `fsharp-compiler-docs`:
+
+
+    cd fsharp-compiler-docs/FSharp.Compiler.Service
+    dotnet restore
+
+
+* Restore the local tools in `fsharp-compiler-docs`:
+
+
+    cd ..
+    dotnet tool restore
+
+
+* Run the documentation tool using your `dotnet/fsharp` fork as input.
+
+
+    dotnet fsdocs watch --eval --sourcefolder ../fsharp/ --input ../fsharp/docs/
+
+
+## Release notes caveat
+
+The release notes pages from `docs/release-notes` are composed from the MarkDown files in subfolders.  
+Changing any of these files, won't regenerate the served webpage. Only the changes to the `.fsx` will trigger the tool. This is a known limitation.