506762f3ff
Currently all core and std macros are automatically added to the prelude via #[macro_use]. However a situation arose where we want to add a new macro `assert_matches` but don't want to pull it into the standard prelude for compatibility reasons. By explicitly exporting the macros found in the core and std crates we get to decide on a per macro basis and can later add them via the rust_20xx preludes.
15 lines
427 B
JavaScript
15 lines
427 B
JavaScript
// exact-check
|
|
|
|
const FILTER_CRATE = 'std';
|
|
|
|
const EXPECTED = {
|
|
'query': 'prinltn',
|
|
'others': [
|
|
{ 'path': 'std', 'name': 'println' },
|
|
{ 'path': 'std::prelude::v1', 'name': 'println' },
|
|
{ 'path': 'std', 'name': 'print' },
|
|
{ 'path': 'std::prelude::v1', 'name': 'print' },
|
|
{ 'path': 'std', 'name': 'eprintln' },
|
|
{ 'path': 'std::prelude::v1', 'name': 'eprintln' },
|
|
],
|
|
};
|