Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Types appearing in error messages should use syntax that the user can write
See original GitHub issueJust got U^ and wondered what it meant. Posting an issue to avoid forgetting it.
Gitter discussion: https://gitter.im/lampepfl/dotty?at=593858217503e2b7061ee7f8
@Blaisorblade: I’ve got
Values of types U^ and U^ cannot be compared with == or !=as a fully user-visible error @DarkDimius: We don’t clean up output from this hints so far. if you’re creative, you may also seeLazyRef(...). Afaik no one has yet seen<overloaded ...>in error message. You could be the first one 😃
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
For started, it’d be helpful if we could distinguish pretty-printing for
-Xprintand pretty-printing for error messages. The former is used for debugging and is free to contain all the crazy syntax we want, the latter is read by users and needs to be as clear as possible.If we use a flag, I’d propose to default this flat to
truein case version ends inSNAPSHOTand false otherwise. Those prints are enabled by default because they save a huge amount of time when you debug typer.