Skip to content

Conversation

hamishknight
Copy link
Contributor

In preparation for removing UnresolvedType in favor of ErrorType, start printing ErrorType as _ unless we've enabled debug printing. <<error type>> should never be presented to the user, instead _ now just consistently means "unknown type".

Use the same set of PrintOptions when printing the results for
different requests.
Use for a few `dump` methods, generic signature debugging, and enable
by default for swift-ide-test.
In preparation for removing UnresolvedType in favor of ErrorType,
start printing ErrorType as `_` unless we've enabled debug printing.
`<<error type>>` should never be presented to the user, instead `_`
now just consistently means "unknown type".
@hamishknight hamishknight force-pushed the wallsocket branch 2 times, most recently from 9bb05d3 to 0bfbe98 Compare September 21, 2025 23:20
@hamishknight
Copy link
Contributor Author

@swift-ci please test

Copy link
Contributor

@ktoso ktoso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, looks good to me.

Does this future direction mean that we should be creating UnresolvedType rather than ErrorType when e.g. distributed fails to find a type of an associated type etc?

@xedin
Copy link
Contributor

xedin commented Sep 22, 2025

It's the other way around :)

@hamishknight
Copy link
Contributor Author

Yeah the goal here is to remove UnresolvedType and just use ErrorType instead

@ktoso
Copy link
Contributor

ktoso commented Sep 22, 2025

Ah got it :-) we've been using ErrorType everywhere so nothing to worry about then, thanks!

Copy link
Contributor

@xedin xedin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll all for removing UnresolvedType. I think it was originally introduced to accommodate CSDiag but we don't really need this anymore.

@hamishknight hamishknight merged commit e64241c into swiftlang:main Sep 23, 2025
5 checks passed
@hamishknight hamishknight deleted the wallsocket branch September 23, 2025 08:30
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.

3 participants