Any reason to not just have a chain of two method calls, rather than a method with "and" - feels like an anti-pattern in a fluent api.