chore: Bump the nuget group with 3 updates

[dependabot]

Updated fable from 5.17.2 to 5.18.0.

Release notes

Sourced from fable's releases.

5.18.0

🚀 Features

• (dart) Add Async runtime and Future interop for dart (#​4978) (b5a337d0)

🐞 Bug Fixes

• Retry MSBuild project cracking serially (#​4991) (b0c6129e)
• (beam) Preserve local spawn calls (#​4992) (70278ec6)
• (dart) Prefix file scope names shadowed by class members (#​4982) (ece7b071)
• (js/ts) Fix Dictionary.Remove and HashSet.Remove to remove empty buckets (#​4985) (aea61b56)
• (js/ts) Clear custom System.Collections.IList implementations (2369fbd2)
• (python) Keep the payload type when reading an erased union field (#​4981) (e0536ecd)
• (rust) Less allocations when enumerating strings (#​4970) (5d62380c)
• (rust) Remove reflection registration on boxing (#​4983) (50a37f78)

⚡ Performance Improvements

• (js/ts) Faster resizeArray.Clear() in JS/TS (32d85add)

View changes on Github

Commits viewable in compare view.

Updated Fable.Core from 5.2.0 to 5.3.0.

Release notes

Sourced from Fable.Core's releases.

5.3.0

🚀 Features

• (beam) Add !^ erased-cast operator to BeamInterop (#​4659) (206776b)

🐞 Bug Fixes

• Add type specifiers to interpolated strings (#​4646) (512ae4d)
• (all) Cli fable clean command crash when output directory doesn't exist (#​4651) (de379e8)
• (all) Align invalidArg error message with .NET format (#​4662) (e672eb7)
• (beam) Preserve element type through Option.Value for interface dispatch (#​4661) (e5521b6)
• (python) Emit wildcard default for union or-patterns (#​4649) (#​4653) (c96f0ec)

View changes on Github

Commits viewable in compare view.

Updated fantomas from 8.0.0 to 8.0.5.

Release notes

Sourced from fantomas's releases.

8.0.5

8.0.5

Changed

• Improved formatting performance. Formatting the source files of dotnet/fsharp allocates around 40% less memory and is roughly 1.4 times faster than 8.0.4, depending on hardware. The fields of WriterEvent, returned by CodeFormatter.GetWriterEventsAsync, are renamed so that cases share them: text for the strings, amount for IndentBy and UnIndentBy, column for the indent and column cases, and nodeType and range for NodeEnd. #​3499
• Update FCS to 'Record the range of the exceptionin SynExceptionDefnRepr', commit 349d6aaf1e4685a72e43b7f4a0708205e4104b4c #​3500

Fixed

• Comment between doc comment and exception keyword gets shifted. The syntax tree had no range for the exception keyword, so a comment between the XML doc or attributes and the keyword was placed in front of the exception name, after the keyword. The parser now records that range, and the comment stays in front of the keyword. #​3483

Special thanks to @​nojaf!

https://www.nuget.org/packages/fantomas/8.0.5

8.0.4

8.0.4

Fixed

• Infix operator with a computation expression on the right-hand side produces invalid code. x := { ... } was read as a computation expression named (:=) x and printed as := x { ... }, which does not compile. It is now an infix application and printed as written. #​3494
• Comment after a parameter of an extern binding with attributes is lost. The range of such a binding stopped at its name, so a comment after one of its parameters was not attached to anything. The binding now spans up to its closing parenthesis. #​3494
• Comment after a parameter of a multiline extern binding gets two spaces in front of it. The comma at the end of the line kept its trailing space, and the comment added its own. #​3494
• in keyword of let! moves to the last and! binding. The parser keeps one in for a let! and its and! bindings, and it always went to the last one. It now stays after the binding it followed. #​3494

Special thanks to @​nojaf!

https://www.nuget.org/packages/fantomas/8.0.4

8.0.3

8.0.3

Fixed

• Second block comment on a line is lost and the next expression moves onto the comment line. A line that holds several comments and no code, such as (* b *) (* c *), was read as one block comment next to code per comment, and there was no code on that line to attach them to. The first one ended up in front of the next expression, pulling it onto the comment line, and the others were dropped. Such a line is now one comment on a line of its own, printed as it was written. #​3487
• Idempotency problem when a comment follows a multiline infix expression in a let binding. A comment on its own line after c + and d, at the column of both, was attached to d rather than to c + d. That made the expression multiline, so the operator moved to the start of the next line, and on the next format the comment went to the whole expression and it was joined onto one line again. An indented comment now goes after the outermost preceding node that starts a line at its column, and only falls back to a node further along a line when there is none. #​3488

Special thanks to @​nojaf!

https://www.nuget.org/packages/fantomas/8.0.3

8.0.2

8.0.2

Fixed

• Code comment inside match-expression leads to additional blank line. A comment that ends the multi-line body of a match clause, and then any blank lines the author kept after it, came out with one blank line more than the source had. The same happened before else, finally, end and the next field of a record, whenever the indented body before them ended in a comment. Since 8.0.0 the unindent that closes such a body leaves the comment's newline at the very end of what was written, and the separator the enclosing construct writes next then opened a second line. Those separators now skip their newline when the comment already wrote one, as the closing brace of a record has done since 8.0.0. Blank lines the author kept, and the ones Fantomas puts between multi-line members and bindings, are unchanged. #​3484

Special thanks to @​nojaf!

https://www.nuget.org/packages/fantomas/8.0.2

8.0.1

8.0.1

Fixed

• Remove TailCall shim from Fantomas.FCS. #​3476
• Fantomas 8 with use bindings in fsx-file. A use at the top level of a script makes the parser warn that it is treated as let, and the check Fantomas runs over its own output refused the file on that warning. The warning is about the source as the author wrote it, not about anything the formatter changed, so it is now one of the warnings the check tolerates. #​3478
• Unexpected de-indent after trivia after expression. A comment at the end of a match that closes a computation expression, or a let body, pushed the closing brace and the next binding one level too far to the right. The unindent before the closing line was placed in front of the comment's newline, where the match still held the column it had claimed and restored its own indent on the way out, undoing the unindent. The newline now moves past those restores, so the line after the comment starts at the outer level. #​3481

Special thanks to @​nojaf!

https://www.nuget.org/packages/fantomas/8.0.1

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions