You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
then calculate will be inferred to be @block. (We can see this in the auto-generated pi.Worker interface.)
I suspect that this bug arises from the fact that this constructor takes an argument. For example, if we change the definition of Result to the following, the procedure is (correctly) inferred to be @duck.
packagepi;
publicclassResult { // a duckable number typeprivateintval;
publicintgetValue() {
returnval;
}
publicvoidsetValue(intval) {
this.val = val;
}
}
The text was updated successfully, but these errors were encountered:
The following type should be duckable.
However, if we return this type from some procedure
then
calculate
will be inferred to be @block. (We can see this in the auto-generatedpi.Worker
interface.)I suspect that this bug arises from the fact that this constructor takes an argument. For example, if we change the definition of
Result
to the following, the procedure is (correctly) inferred to be @duck.The text was updated successfully, but these errors were encountered: