Skip to content
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

Match messages with multispans and multiple messages on a line #42

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

pczarn
Copy link
Contributor

@pczarn pczarn commented Aug 3, 2016

Fixes #41

Example of an expected error that matches 2 actual errors

// Should get errors for both 'Some' and 'None'
use std::option::Option::{Some, None}; //~ ERROR*2 unused import

For example '9' in `//~ ERROR*9 foo`
Duplicate actual errors are allowed by default. Errors with
multispans are considered as duplicated for each sub-span.
This is a [breaking-change] to compiletest's behavior.
@pczarn
Copy link
Contributor Author

pczarn commented Aug 3, 2016

I'm not sure about making the change in behavior for multiple messages. Should the following expected error match two actual errors?

// Should get errors for both 'Some' and 'None'
use std::option::Option::{Some, None}; //~ ERROR unused import

Copy link
Contributor

@dtolnay dtolnay left a comment

Choose a reason for hiding this comment

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

This should be added upstream in rust-lang/rust first (https://github.com/rust-lang/rust/tree/master/src/tools/compiletest). Then it will be picked up by this crate.

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.

None yet

2 participants