Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 6,026 | Comments: 44,842

filter by tags archive

Inline Anonymous Visitors

time to read 2 min | 291 words

One of the most common chores when working with compilers is the need to create special visitors. I mean, I just need to get a list of all the variables in the code, but I need to create a visitor class and execute it in order to get the information out. This is not hard, the code is something like this:

public class ReferenceVisitor : DepthFirstVisitor
     public List<string> References = new List<string>();
     public void OnReferenceExpression(ReferenceExpression re)
public bool IsCallingEmployeeProperty(Expression condition)
    var visitor = new ReferenceVisitor();
    return visitor.References.Contains("Employee"); 

Doing this is just annoying. Especially when you have to create several of those, and they make no sense outside of their call site. In many ways, they are to compilers what event handlers are to UI components.

What would happen if we could create a special visitor inline, without going through the "create whole new type" crap? I think that this would be as valuable as anonymous delegates and lambdas turned out to be. With that in mind, let us see if I can make this work, shall we?

public bool IsCallingEmployeeProperty(Expression condition)
	var references = new List<string>();
	new InlineVisitor
		OnRefefenceExpression = re => references.Add(re.Name) 
	return references.Contains("Employee"); 

Especially in the more moderately complex scenarios, such a thing is extremely useful.



To make it even more concise, add a static utility method:


InlineVisitor.Visit(condition, re => references.Add(re.Name));

Ayende Rahien

Not really, this would work if and only if I wanted to run only over ReferenceExpression, and I want this over the entire AST.


[NOTE: I have no idea what you are talking about. I have not built compilers (yet) and I do now know what visitors are. But...]

I don't see why you can't make such a class:

public class InlineVisitor : DepthFirstVisitor


 public Action<ReferenceExpression> OnReferenceExpressionHandler { private get; set; }

 public void OnReferenceExpression(ReferenceExpression re)





which you would use exactly as you specified.

Or is that exactly what you intended to do?

Ayende Rahien

That is exactly what I was referring to.


How is this used, if you don't mind me asking?

I mean, who calls that OnReferenceExpression method?

Ayende Rahien

Just like your code is doing, by the actual DepthFirstVisitor

Andrey Shchekin

I just understood what it reminds me of:

Mock(mock => {

    mock.Expect(x => x.OnReferenceExpression(...))

              .Callback(re => references.Add(re.Name))


which is much uglier than what you propose, bt is not limited to visitors. Just rename Mock to something fitting, like Inline<>.

As for uglyness,

new Inline {

     { x => x.OnReferenceExpression(null), re => references.Add(re.Name) }


I think with a ton of overloads for Add(,) it may be viable.

Comment preview

Comments have been closed on this topic.


No future posts left, oh my!


  1. Technical observations from my wife (3):
    13 Nov 2015 - Production issues
  2. Production postmortem (13):
    13 Nov 2015 - The case of the “it is slow on that machine (only)”
  3. Speaking (5):
    09 Nov 2015 - Community talk in Kiev, Ukraine–What does it take to be a good developer
  4. Find the bug (5):
    11 Sep 2015 - The concurrent memory buster
  5. Buffer allocation strategies (3):
    09 Sep 2015 - Bad usage patterns
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats