You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The and and or matcher implementations are restricted to use by AbstractMatcher, unlike the not (and other matchers in this class) matcher - would it be possible to expose these as Matchers.and(a, b) and Matchers.or(a, b)? This would allow use of these matchers without extending AbstractMatcher for the default implementation, or creating your own matchers.
Reacted by Chen Liang, Logan Speck and Parker Lougheed
The and and or methods in Matcher could be default implemented now that Guice requires Java 8 - is this something that might be considered now, or is this a dead idea?
Activity
cterse commentedon May 24, 2021
Its been quite long since this issue was opened. Can I look into this?
kashike commentedon May 25, 2021
@cterse see #1200
kashike commentedon Apr 29, 2023
The
andandormethods inMatchercould bedefaultimplemented now that Guice requires Java 8 - is this something that might be considered now, or is this a dead idea?sameb commentedon Apr 29, 2023
Yeah, that sounds reasonable.