0.7.1 - This version is safe to use because it has no known security vulnerabilities at this time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform
Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.
Apache-2.0 - Apache License 2.0
Find the crate name from the current Cargo.toml.
When writing declarative macros, $crate representing the current crate is
very useful, but procedural macros do not have this. If you know the current
name of the crate you want to use, you can do the same thing as $crate.
This crate provides the features to make it easy.
Add this to your Cargo.toml:
[dependencies]
find-crate = "0.7"find_crate function gets the crate name from the current Cargo.toml.
use find_crate::find_crate;
use proc_macro2::{Ident, Span, TokenStream};
use quote::quote;
fn import() -> TokenStream {
let name = find_crate(|name| name == "foo").unwrap().name;
let name = Ident::new(&name, Span::call_site());
// If your proc-macro crate is 2018 edition, use `quote!(use #name as _foo;)` instead.
quote!(extern crate #name as _foo;)
}As in this example, it is easy to handle cases where proc-macro is exported from multiple crates.
use find_crate::find_crate;
use proc_macro2::{Ident, Span, TokenStream};
use quote::quote;
fn import() -> TokenStream {
let name = find_crate(|name| name == "foo" || name == "foo-core").unwrap().name;
let name = Ident::new(&name, Span::call_site());
// If your proc-macro crate is 2018 edition, use `quote!(use #name as _foo;)` instead.
quote!(extern crate #name as _foo;)
}Using Manifest to search for multiple crates. It is much more efficient
than using find_crate function for each crate.
use find_crate::Manifest;
use proc_macro2::{Ident, Span, TokenStream};
use quote::{format_ident, quote};
const CRATE_NAMES: &[&[&str]] = &[
&["foo", "foo-core"],
&["bar", "bar-util", "bar-core"],
&["baz"],
];
fn imports() -> TokenStream {
let mut tokens = TokenStream::new();
let manifest = Manifest::new().unwrap();
for names in CRATE_NAMES {
let name = manifest.find(|name| names.contains(&name)).unwrap().name;
let name = Ident::new(&name, Span::call_site());
let import_name = format_ident!("_{}", names[0]);
// If your proc-macro crate is 2018 edition, use `quote!(use #name as #import_name;)` instead.
tokens.extend(quote!(extern crate #name as #import_name;));
}
tokens
}By default it will be searched from dependencies and dev-dependencies.
This behavior can be adjusted by changing the [Manifest::dependencies] field.
find_crate and Manifest::new functions read Cargo.toml in
CARGO_MANIFEST_DIR as manifest.
If you write function-like procedural macros, you can combine it with declarative macros to support both crate renaming and macro re-exporting.
This crate is intended to provide more powerful features such as support for multiple crate names and versions. For general purposes, proc-macro-crate, which provides a simpler API, may be easier to use.
Licensed under either of Apache License, Version 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.