I think even the visitor pattern isn't required here, all you need is subclassing. Although this clutters things up more by having abstract methods in the base class, technically that's all you need.
Re:Ask HN: Why Haskell?
by SamReidHughes on Monday March 31, 2014 @10:43PM
(#7505844)
Sure.
An example of the visitor pattern:
This is equivalent to the Haskell code including the fact that in this example the objects are immutable.Instead of using a case expression to pattern match over the player, you'd have to construct a PlayerVisitor and implement the visit methods on that type.
Things can be made a bit less cumbersome than that, for example in a language with lambdas, you can just have the Visit method take a lambda for each subclass, and each subclass's implementation calls one. That makes it arguably equally convenient to use the types (with some extra parentheses), but it's still much more annoying to define the types that way in the first place.