Branch: refs/heads/main
Revision: 3af3fd2
Author: mppf
Log Message:
Merge pull request #18029 from mppf/override-hijack-future
Add a future for an override hijack case
This PR adds a test that I think should keep working (because tertiary overrides with new method names make the visitor pattern easy) and a future case that is problematic (and arguably a case of hijacking).
See issue #16854 which discusses whether some tertiary overrides should be errors.
Test change only - not reviewed.
Modified Files:
A test/functions/ferguson/hijacking/tertiary-class-method-override-bad.bad
A test/functions/ferguson/hijacking/tertiary-class-method-override-bad.chpl
A test/functions/ferguson/hijacking/tertiary-class-method-override-bad.future
A test/functions/ferguson/hijacking/tertiary-class-method-override-bad.good
A test/functions/ferguson/hijacking/tertiary-class-methods-override-ok.chpl
A test/functions/ferguson/hijacking/tertiary-class-methods-override-ok.good
Compare: https://github.com/chapel-lang/chapel/compare/70b424bdda98...3af3fd2d1e3f