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
Right now, a background prerequisite always is implicitly tagged with :times (range 0). If a user explicitly specifies a :times, that should be obeyed.
The text was updated successfully, but these errors were encountered:
I'm disliking this idea now. For a provided prerequisite, it's clear where the how-many-times-called check happens. When does the check for a wrapping background check happen? At exit from the fact? I think the complexity is unwarranted for a feature not-that-often used.
Reopening because I think it is worth looking into addressing.
I've seen some tests that use :times with against-background, which basically doesn't do anything, so it would be good to get this sorted to prevent confusion and make sure tests are checking what they expect to check
If going for a fix of this behavior, worth looking at #54 as well
Right now, a background prerequisite always is implicitly tagged with
:times (range 0)
. If a user explicitly specifies a:times
, that should be obeyed.The text was updated successfully, but these errors were encountered: