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
It appears to be using plain numerical == comparison.
is_refcount( $cb, Test2::Tools::Compare::validator( sub { $_ > 1 } ),
'$cb has refcount > 1 captured by followed_by callback' );
causes:
# Failed test '$cb has refcount > 1 captured by followed_by callback'
# at ./t/06followed_by.pl line 29.
# expected Test2::Compare::Custom=HASH(0x55604b89b340) references, found 2
It'd be handy to support proper use of check objects - especially when combined with Test-More/Test2-Suite#258 - as this would permit
is_refcount( $cb, number_gt(1), '$cb has refcount > 1 captured by followed_by callback' );
The text was updated successfully, but these errors were encountered:
Adding more tools that emulate is() makes little sense. Though under the hood you could wrap the is() code in refcount_is() to support refcount_is($thing, $check) that opens the door for checking that the refcount is a hash or has a deeply nested structure.
We talked in person and decided on this interface:
is($thing, refcnt(5), "refcount is 5");
is($thing, refcnt(5,10), "refcount is between 5 and 10");
is($thing, refcnt($check), "refcount matches the specified check");
refcnt() is not necessarily the name to use, but similar.
It appears to be using plain numerical
==
comparison.causes:
It'd be handy to support proper use of check objects - especially when combined with Test-More/Test2-Suite#258 - as this would permit
The text was updated successfully, but these errors were encountered: