On Wed, Jun 9, 2010 at 2:24 PM, Earwin Burrfoot <email@example.com>
> Can we represent the QueryNo. You could go for unified interface that allows you to express
> state in some general structure, that no matter which Query you get, you'll
> know how to score it?
different query states, like a set of untyped key-values, but you'll
end up switching on these keyvalues in the end.
It's better to define a set of matchers, and then produce visitors
that compute scores. These visitors are then free to specialize on
matchers or not, or ignore the whole tree completely.