Message298177
Generally the called with asserts can only be used to match the *actual call*, and they don't determine "equivalence".
To do it cleanly would be tricky, and adding complex code is a maintenance burden. I'm not convinced there's a massive use case - generally you want to make asserts about what your code actually does - not just check if it does something equivalent to your assert.
So I'm not enthusiastic about this. |
|
Date |
User |
Action |
Args |
2017-07-11 19:04:51 | michael.foord | set | recipients:
+ michael.foord, rhettinger, Max Rothman |
2017-07-11 19:04:51 | michael.foord | set | messageid: <1499799891.86.0.476722409403.issue30821@psf.upfronthosting.co.za> |
2017-07-11 19:04:51 | michael.foord | link | issue30821 messages |
2017-07-11 19:04:51 | michael.foord | create | |
|