Rename Treenumerator -> TreeEnumerator

This commit is contained in:
Ryan Nowak 2018-06-01 20:39:34 -07:00
parent 8906d8e5f7
commit dc4be30d88
3 changed files with 4 additions and 4 deletions

View File

@ -67,7 +67,7 @@ namespace Microsoft.AspNetCore.Routing.Matchers
var tree = cache[i]; var tree = cache[i];
var tokenizer = new PathTokenizer(httpContext.Request.Path); var tokenizer = new PathTokenizer(httpContext.Request.Path);
var treenumerator = new Treenumerator(tree.Root, tokenizer); var treenumerator = new TreeEnumerator(tree.Root, tokenizer);
while (treenumerator.MoveNext()) while (treenumerator.MoveNext())
{ {

View File

@ -8,12 +8,12 @@ using Microsoft.AspNetCore.Routing.Internal;
namespace Microsoft.AspNetCore.Routing.Tree namespace Microsoft.AspNetCore.Routing.Tree
{ {
internal struct Treenumerator : IEnumerator<UrlMatchingNode> internal struct TreeEnumerator : IEnumerator<UrlMatchingNode>
{ {
private readonly Stack<UrlMatchingNode> _stack; private readonly Stack<UrlMatchingNode> _stack;
private readonly PathTokenizer _tokenizer; private readonly PathTokenizer _tokenizer;
public Treenumerator(UrlMatchingNode root, PathTokenizer tokenizer) public TreeEnumerator(UrlMatchingNode root, PathTokenizer tokenizer)
{ {
_stack = new Stack<UrlMatchingNode>(); _stack = new Stack<UrlMatchingNode>();
_tokenizer = tokenizer; _tokenizer = tokenizer;

View File

@ -177,7 +177,7 @@ namespace Microsoft.AspNetCore.Routing.Tree
var tokenizer = new PathTokenizer(context.HttpContext.Request.Path); var tokenizer = new PathTokenizer(context.HttpContext.Request.Path);
var root = tree.Root; var root = tree.Root;
var treeEnumerator = new Treenumerator(root, tokenizer); var treeEnumerator = new TreeEnumerator(root, tokenizer);
// Create a snapshot before processing the route. We'll restore this snapshot before running each // Create a snapshot before processing the route. We'll restore this snapshot before running each
// to restore the state. This is likely an "empty" snapshot, which doesn't allocate. // to restore the state. This is likely an "empty" snapshot, which doesn't allocate.