There is currently a not-insignificant amount of code dedicated to dynamic conjunctions. In reality though, I've grown to doubt it adds much utility to the API. I'm guessing over 95% of use cases would be covered by is()/does()/has()/should()/will(). Part of my theory was also that it could be helpful for non-English speakers, but the rest of the API is in English, so does it really add that much? And all this at the expense of code complexity and lack of clarity for return types.
Make concrete conjunction functions
Possibly in a trait just to keep them localized somewhere
Pull in the other examples I'd relegated to examples in the documentation
There is currently a not-insignificant amount of code dedicated to dynamic conjunctions. In reality though, I've grown to doubt it adds much utility to the API. I'm guessing over 95% of use cases would be covered by
is()/does()/has()/should()/will(). Part of my theory was also that it could be helpful for non-English speakers, but the rest of the API is in English, so does it really add that much? And all this at the expense of code complexity and lack of clarity for return types.