lateapexearlyspeed-issue-30778 Create method: TryReadExact().

[lateapexearlyspeed]

Fix #30778
Will change PR to normal status when it is ready for review, thanks.

[dotnet-issue-labeler]

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

[ghost]

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

Issue Details

---

Fix #30778
Will change PR to normal status when it is ready for review, thanks.

Author:	lateapexearlyspeed
Assignees:	-
Labels:	area-System.Buffers, new-api-needs-documentation
Milestone:	-

[jeffhandley]

Looks good to me with 1 comment formatting suggestion. I'd like to get a secondary review from @tannergooding, @davidfowl, or @GrabYourPitchforks though.

[davidfowl]

The implementation looks fine but I'm wondering if there's a more optimal implementation. Can we add benchmarks for this new method?

[lateapexearlyspeed]

The implementation looks fine but I'm wondering if there's a more optimal implementation. Can we add benchmarks for this new method?

Hi @davidfowl Sorry I am not very familiar with workflow of adding benchmark. Because it is new method, is that dotnet runtime repo publishes new pack then perf repo references that new dotnet pack so that it can build to get new method ?

[jeffhandley]

@lateapexearlyspeed The instructions are here: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md#benchmarking-workflow-for-dotnetruntime-repository

Let us know if you have any trouble getting that set up.

@davidfowl Any objections to merging this implementation as-is so long as we follow up with adding a new benchmark to dotnet/performance? Or do you want to see the (new, local) benchmark results before we merge?

[davidfowl]

I'm fine merging it with the benchmark as a follow up

[jeffhandley]

Thanks for the contribution, @lateapexearlyspeed! #60332 was filed for creating the microbenchmarks. If you're interested in contributing the new benchmarks, please leave a comment on that issue and I can assign it to you.