I am not arguing about the name. If that needs to be different, fine. Maybe the issue I see is more driven from the variable name used in `GroupOperation`. In this class we hold an instance of `ExposedFields` (which can hold both synthetic and non-synthetic fields) but only store synthetic fields in it. Without realizing the latter simply calling `….isEmpty()` creates the impression we check for whether there are no synthetic and non-synthetic fields present. So we're using a method here that semantically only makes sense, because we use the type in a certain way. I'd argue adding a `hasNonSyntheticFields()` method only checking the non-synthetic fields is semantically clearer - both on the type *and* on the client side using the type in a very special way.