Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.

@dotnet/area-system-io-hashing please review this package readme PR before EOW so that we can get the change still ported into .NET 8.

@eNeRGy164 looks like your branch has a conflict (it adds 523 commits)

@eNeRGy164 looks like your branch has a conflict (it adds 523 commits)

Yes, I pressed the "fork sync" button on the wrong branch 😭
Will fix this in a second

Sorry for all the reviewers that suddenly were added to this PR 👀

Tagging subscribers to this area: @dotnet/area-system-io-hashing, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.

@eNeRGy164 By the by, it's generally frowned upon to do a squash/amend during a PR (anything requiring a force-push). It makes it harder to review what got changed as a response to the feedback. (We squash it up when merging)

Yeah, there's a github feature to look at what changed in a force push, but doesn't exist in the Files changed tab/view. But, in general, the preferred form is to leave the individual commits once a PR has started.

@eNeRGy164 By the by, it's generally frowned upon to do a squash/amend during a PR (anything requiring a force-push). It makes it harder to review what got changed as a response to the feedback. (We squash it up when merging)

Thanks for pointing that out. I didn't notice the mention on squash commit.
I'm used to work at repos where clean git history is valued, and one should not create review commits.