MatchExpression subclasses implement the equivalent() virtual method, which take another MatchExpression and return a boolean indicating whether the two expressions represent the same predicate.

The implementation of GeoMatchExpression::equivalent() was never finished (see code here). This can make testing cumbersome, especially in the query planner unit tests as these tests use MatchExpression::equivalent() to verify that the planner is using the correct filters.