Using 'dynamic' in C# to implement Visitor Pattern

Question

I have an application where I am performing an operation on a series of elements and the exact nature of the operation depends on the type of the element being operated upon

Answer 1

Yes, I was considering this approach, but decided against it for a more traditional approach. I derive each visitor from an interface that has Visit methods for each type I want to implement the operation for.

If you have a number of different operations you want to implement as visitors, eg. Save and Load operations, and you might want to add more in the future; with the dynamic approach you don't get compilation errors if you forget to implement your operation for one of the types you need to handle. You'll only find out when the program crashes and burns at runtime.

I want to be sure at compile time that any operation has been implemented for all of the possible types.