Skip to content

Better printing of capabilities in error messages #23701

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Aug 9, 2025

  • Special case in some situations so that we only print the name,
    not the underlying type.
  • Print TermParamRefs like other singleton types

If the closure has an expected function type with a fully defined result type,
take the internalized result type as the local return type of the closure.

This has the effect that some conformance tests are now done with Fresh instead Result
caps. This means a now can widen a local reference to a result cap, since the comparison
is done between the local reference and the internalized FreshCap. Previously this failed
since we compared a local cap with result cap, and result caps only subtype other result caps.

It also propagates types more aggressively into closure bodies, which sometimes reduces the
error span and improves the error message.
 - Special case in some situations so that we only print the name,
   not the underlying type.
 - Print TermParamRefs like other singleton types
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant