mirror of
https://github.com/xoofx/markdig.git
synced 2026-02-03 21:36:36 +00:00
[PR #828] [MERGED] Add .NET 9 target, drop .NET 6 #1237
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/xoofx/markdig/pull/828
Author: @MihaZupan
Created: 11/30/2024
Status: ✅ Merged
Merged: 12/17/2024
Merged by: @xoofx
Base:
master← Head:net90📝 Commits (3)
98a060fAdd .NET 9 target, drop .NET 6455f8f3Fix dotnet-versions format4078173Tweak SpecFileGen paths📊 Changes
7 files changed (+14 additions, -10 deletions)
View changed files
📝
.github/workflows/ci.yml(+4 -1)📝
src/Markdig.Tests/Markdig.Tests.csproj(+5 -4)📝
src/Markdig.Tests/TestYamlFrontMatterExtension.cs(+1 -1)📝
src/Markdig/Helpers/FastStringWriter.cs(+1 -1)📝
src/Markdig/Markdig.targets(+1 -1)📝
src/SpecFileGen/SpecFileGen.csproj(+1 -1)📝
src/global.json(+1 -1)📄 Description
Unlike in the past, there is now a reason to bump TFMs even when not explicitly using new APIs due to language changes that can target better overloads when recompiling (e.g.
params spanorOverloadResolutionPriority).I don't know of any places where that would kick in for Markdig right now, but there are some neat new APIs in 9.0 that might be interesting to play with here.
I've also added back older TFMs to the test project so we're not completely without coverage (given we have a bit of conditionally-compiled code & polyfills). Skipped framework though cuz CI was being weird 🤷♂️
Some initial numbers without any Markdig changes on a large document (.NET 9 perf blog post ~570 KB):
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.