FileStream.Position breaking change documentation should be deleted

[mriehm]

Describe the issue or suggestion

This article describes a breaking change that supposedly occurs in .NET 6:
https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/6.0/filestream-position-updates-after-readasync-writeasync-completion

However, it seems that breaking change was reverted before .NET 6 was released, so it is misleading to continue to list that breaking change. I think that article should be deleted.

The supposed breaking change is that FileStream.Position is now updated only after ReadAsync/WriteAsync completes in .NET 6. That breaking change article was drafted on May 5, 2021, but then there was a PR entitled 'Update position before ReadAsync starts, but fix it after incomplete read' on July 29, 2021. So, I think the breaking change article was just not revisited after this later PR.

I've run the sample code provided in the breaking change article on .NET 8, both Windows and WSL, and it matches the pre-.NET 6 behavior described in that article, not the .NET 6+ behavior described.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: c2cd1391-c58f-1041-963e-a580fb5b1a27
• Version Independent ID: 3b97de24-fc59-5b0e-8921-5d2344dc87ac
• Content: .NET 6 breaking change: FileStream.Position updated after ReadAsync or WriteAsync completion - .NET
• Content Source: docs/core/compatibility/core-libraries/6.0/filestream-position-updates-after-readasync-writeasync-completion.md
• Service: dotnet-fundamentals
• GitHub Login: @gewarren
• Microsoft Alias: gewarren

---

Associated WorkItem - 250223

[gewarren]

Thanks @mriehm. I'm going to keep the breaking change article but update it according to dotnet/runtime#56531 (comment).