Cannot handle type annotation that's the same as the expected type
I had a rule like the following which type-checked and everything, but that got me a lot of
Permise failure: [Lots of ATerms here]. And it didn’t generate theexec_defaultmethod for theFor_2class.Scope sc |- s@For(ib, st : Statement) --> CAndStar([c1, c2]) where Scope sc, Pos spos(s) |- ib -sc-> ScC(sc',c1) , Scope sc' |- st --> c2I found out that the problem was with the type annotation.
Submitted by Jeff Smits on 9 May 2015 at 03:04stis already aStatement, nothing special going on there, no need to use another arrow to get aStatement. So the type annotation was redundant. Once removed this problem went away. I’m fine with supporting or forbidding these redundant type annotations, but the runtime failure kept me busy for a few hours, trying to find out which of my changes caused it :)
Log in to post comments