Community
Participate
Working Groups
Right now, if some bindings are problem binding on the compiler side, we do return them as normal binding on the dom/ast side. I think we need two modes: - strict mode: problem binding => return null on the dom/ast - fuzzy mode: problem binding => return a binding not null on dom/ast if the error can be handled (visibility problem for example). See bug 81544 comment 11.
Jim, Do you think this could be explained in the specs?
This can slow down the conversion. The compiler doesn't always create problem bindings. So I would not push to get a dual mode.
Copying bug 81544 comment 25 and adding CCs. The current solution (returning a generic type binding for half-way resolved bindings) conflicts with bug 80472. When I get a generic binding, I don't know whether it's generic because of bug 80472 or because type arguments could not be resolved. I think we can ship 3.1 with the current solution, but this should definitely be discussed again for 3.2.
See also bug 101955.
defer post 3.2
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.