WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
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
Avoid more constraints in result if trying views (#24369)
In `canProfitFromMoreConstraints`, balk if
`mode.is(ImplicitExploration)`.
The failing case was due to the `constrainResult` "up the stack" in
`adaptNoArgs`, which drove type comparisons and completions, including a
conversion. The `FunProto` context had a console reporter that emitted
the errors encountered, not an exploring reporter.
The justification is that "more constraints" is motivated by arg
inference, so if the arg is already involved in views, further
information in the result is not needed, especially at the cost of
spurious exploratory errors using a context that doesn't reflect the
current mode.
Fixes#24192
0 commit comments