yog-script-analyze 0.2.4

Yog Script (.ys, .yns) analyzed: its lexer, parser and syntax tree, names resolved, the class index model — what the build and the editors read a source with.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

//! Procedural macros (`ys.md` §3, Attributes and macros): written in Yog
//! Script and run by whoever builds — this crate only asks. A call
//! `Name!(…)` no declared macro takes, each `[Derive(Name)]` on a type and
//! each attribute macro's `[Name(…)]` are handed over as text; the code
//! given back is read in their place.

/// What runs the procedural macros a build has.
pub trait ProcMacros {
    /// `name!(input)`: the code it writes, or why it failed; `None`: no
    /// such macro.
    fn call(&self, name: &str, input: &str) -> Option<Result<String, String>>;

    /// `[Derive(name)]` on the declaration written `item`: the code added
    /// after it.
    fn derive(&self, name: &str, item: &str) -> Option<Result<String, String>>;

    /// `[name(args)]`, an attribute macro, on the declaration written
    /// `item`: the code that takes the declaration's place.
    fn attribute(&self, name: &str, args: &str, item: &str) -> Option<Result<String, String>>;
}