about summary refs log tree commit diff
path: root/src/test/ui/continue-after-missing-main.stderr
AgeCommit message (Collapse)AuthorLines
2022-05-08Move some tests to more reasonable placesCaio-19/+0
2022-03-05Do not point at whole file missing `fn main`Esteban Kuber-9/+3
Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be *worse*. This change will make it so that VSCode will *not* underline the whole file when `main` is missing, so other errors will be visible.
2019-11-07Update ui testsGuillaume Gomez-1/+2
2019-11-03Avoid mixing error patterns with error annotationsTomasz Miąsko-3/+3
When both error patterns and error annotations are present in an ui test, only error patterns are validated against the output. Replace the error pattern with an error annotation to avoid silently ignoring the other error annotation.
2019-09-14Provide a span if main function is not present in crateMark Rousskov-1/+9
Unfortunately, the diagnotic machinery does not cope well with an empty span which can happen if the crate is empty, in which case we merely set a spanless note.
2019-04-18hide `--explain` hint if error has no extended infoAndy Russell-2/+1
2019-04-11Continue evaluating after missing mainEsteban Küber-0/+17