Possible bug with explicit @Duck procedure

[dwtj]

(I haven't really looked at this carefully, but I wanted to put this here before I forget.)

The following example appeared to make the annotation processor stop responding (i.e. in Eclipse, sources were no longer being generated).

package types;

public interface Tree {
	int numChildren();
	// ...
}

package ex;

import org.paninij.lang.Capsule;
import org.paninij.lang.Duck;

import types.Tree;

@Capsule
class ServerCore {
	@Duck Tree getTree() {
		Tree t = null;
		// ...
		return t;
	}
}

However, the issue goes away once the explicit @Duck annotation is removed.

As usual, it will probably be easier to debug this by doing so on the CLI rather than in the IDE.

[dwtj]

Once @Duck is removed, it looks like the generated source is marking getTree() as @Block. Hmmm...

[dwtj]

But then, if you make Tree be a class rather than an interface, the generated source marks getTree() as @Duck.

I bet that this is a problem with the procedure annotation inference code. Or maybe two problems... Here are my guesses:

• The IDE locks up because an exception is being thrown and crashing the annotation processor.
• The annotation inference code doesn't correctly handle the case that a return type is an interface type.

[dwtj]

Related? #139