We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The following performance regressions occurred between the Preview 4 snapshot (May 2nd, 2023) and Preview 7 snapshot (July 19th, 2023).
The configuration used for the benchmarks is Mono AOT with LLVM on x64 ubuntu 18.04.
The text was updated successfully, but these errors were encountered:
@MihaZupan Some of them may have regressed in #87621.
/cc: @vargaz
Sorry, something went wrong.
That change should be cosmetic only
-bool someCondition = span.IndexOfAnyExcept(foo) >= 0; +bool someCondition = span.ContainsAnyExcept(foo); static bool ContainsAnyExcept(Span, value) => span.IndexOfAnyExcept(value) >= 0;
I suppose it's possible you could get worse codegen for some of these, but the differences here are way too excessive.
Besides, none of these benchmarks look like they'd be hitting the changed code.
Since this is about .net 8, there's really not much action to take here. Closing.
No branches or pull requests
Description
The following performance regressions occurred between the Preview 4 snapshot (May 2nd, 2023) and Preview 7 snapshot (July 19th, 2023).
The configuration used for the benchmarks is Mono AOT with LLVM on x64 ubuntu 18.04.
The text was updated successfully, but these errors were encountered: