aspnetcore/benchmarks/Microsoft.AspNetCore.Routin.../Matching
Ryan Nowak 9db2833fc2 Make endpoint selector policies per-candidate-set
This allows us to filter `IEndpointSelectorPolicy` instance based on
whether the apply to a given candidate set. This should allow us to
remove some HAXXX from MVC.

The idea here is the ESP becomes much more pay-for-play if you can
statically eliminate many of the cases where it would usually no op.
2018-10-05 21:03:59 -07:00
..
FastPathTokenizerBenchmarkBase.cs
…
FastPathTokenizerEmptyBenchmark.cs
…
FastPathTokenizerLargeBenchmark.cs
…
FastPathTokenizerPlaintextBenchmark.cs
…
FastPathTokenizerSmallBenchmark.cs
…
JumpTableMultipleEntryBenchmark.cs
…
JumpTableSingleEntryBenchmark.cs
…
JumpTableZeroEntryBenchmark.cs
…
MatcherAzureBenchmark.cs Rename EndpointFeature -> EndpointSelectorContext 2018-09-30 14:09:59 -07:00
MatcherAzureBenchmarkBase.generated.cs
…
MatcherBuilderAzureBenchmark.cs
…
MatcherBuilderGithubBenchmark.cs
…
MatcherBuilderMultipleEntryBenchmark.cs
…
MatcherGithubBenchmark.cs Rename EndpointFeature -> EndpointSelectorContext 2018-09-30 14:09:59 -07:00
MatcherGithubBenchmarkBase.generated.cs
…
MatcherSingleEntryBenchmark.cs Rename EndpointFeature -> EndpointSelectorContext 2018-09-30 14:09:59 -07:00
RouteEndpointAzureBenchmark.cs
…
TrivialMatcher.cs Rename EndpointFeature -> EndpointSelectorContext 2018-09-30 14:09:59 -07:00
TrivialMatcherBuilder.cs
…