Ensure URB's are resolved before performing visibility checks.#4647
Conversation
srikanth-sankaran
commented
Nov 21, 2025
- Fixes The type ... from the descriptor computed for the target context is not visible here #4632
|
This problem goes back to the original implementation of lambda expressions. While checking whether the computed SAM descriptor is "kosher", we must ensure all types mentioned in the SAM (return types, enclosing types, arguments, thrown exceptions etc.,) are visible at the lambda invocation site. While doing these checks we may end up with an @stephan-herrmann - since you are fascinated by bugs that have managed to hide for a long time, you may want to study this one 😆 @iloveeclipse @jarthana - Let me know if you want this for 4.38 - On the one hand, this bug has been there from day 1 and so perhaps could wait for 4.39. On the other hand, the fix is simple so we could consider this fix for 4.38 RC1/RC2 - I guess it is too late for RC1. (PR still under test - I don't expect any failures - famous last words 😆) |
Jay and I discussed this offline and decided we will release this as soon as the tree opens for 4.39. I looked through bugzilla and github issues tracker for similar defect reports and didn't find any. This seems one off case and given it is not a regression, it is prudent to wait for 4.38 to ship. |
I fully agree with that |
34acf5a to
d645762
Compare
|
This pull request changes some projects for the first time in this development cycle. An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch. Git patchFurther information are available in Common Build Issues - Missing version increments. |
005178f to
a2881c7
Compare