Validate argument amount in old(...) calls

[Vampire]

Previously if you had multiple arguments to an old(...) call 2nd and on were simply ignored,
and if you had no argument the compiler throws a NullPointerException.

Now the compiler validates that there is exactly one argument to an old(...) call.

Due to the multiple arguments now being forbidden, this is theoretically a breaking change,
but until recently the whole feature was not even documented and probably very few people
use it at all, let alone with multiple arguments.

[Vampire]

Current dependencies on/for this PR:

• master
  • PR Validate argument amount in old(...) calls #1810 👈

This comment was auto-generated by Graphite.

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (4b325b3) 0.00% compared to head (3b646bd) 80.57%.

Additional details and impacted files

@@              Coverage Diff              @@
##             master    #1810       +/-   ##
=============================================
+ Coverage          0   80.57%   +80.57%     
- Complexity        0     4250     +4250     
=============================================
  Files             0      434      +434     
  Lines             0    13261    +13261     
  Branches          0     1686     +1686     
=============================================
+ Hits              0    10685    +10685     
- Misses            0     1961     +1961     
- Partials          0      615      +615     

Files	Coverage Δ
...org/spockframework/compiler/DeepBlockRewriter.java	98.23% <100.00%> (ø)

... and 433 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[leonard84]

thanks @Vampire