Community
Participate
Working Groups
For 118754 I have committed a change to modify checks like this: 'type == MISSING' to be 'type.isMissing()' this was required for LTW. It may impact the ability for us to proceed with MissingWithKnownSignature types since they return 'true' for isMissing() but don't pass the 'type==MISSING' test. When Ron complains about new bunches of cant find type messages, we should look at where they are are change the isMissing calls to isReallyMissing() or something similar. The tests all passed with the above change in place, so I can only assume we don't have anything that verifies the right number of cant find type messages come out when weaving something when we don't know all its dependencies.
placeholder bug for googling in the future :) Closing
closing.
Just as a note...the referenced bug is bug 117854 (not 118754).