# Misses
**Misses** is a DSL compiler that transforms `.mrs` macro definitions into ready-to-use Rust proc macro source files. Write your macro once in a concise, readable syntax; Misses generates the full `syn`/`quote` boilerplate for you.
---
## Why Misses?
Writing proc macros means wrestling with `syn` parsing, `quote!` boilerplate, error handling, and variadic patterns. You write the same patterns over and over.
**Misses lets you write the macro once, in readable syntax, and generates all the boilerplate for you.**
Here's a real example:
### `derive_getters.mrs`
```mrs
macro derive_getters! {
struct $name:ident { $($field:ident : $ty:ty),* } => {
T~{
impl $name {
for field in $fields =>
pub fn $field.name(&self) -> &$field.ty { &self.$field.name }
}
}
}
}
```
Generated output
```rust
extern crate proc_macro;
#[proc_macro]
pub fn derive_rpc(input: proc_macro::TokenStream) -> proc_macro::TokenStream {
let input = proc_macro2::TokenStream::from(input);
use quote::format_ident;
let (name, params, ret) = {
use syn::parse::Parser as _;
let __parser = |
_input: syn::parse::ParseStream,
| -> syn::Result<(syn::Ident, Vec<(syn::Ident, syn::Type)>, syn::Type)> {
let name: syn::Ident = _input.parse()?;
let params = {
let mut __f = Vec::new();
while !__brace_content.is_empty() {
let __fn: syn::Ident = __brace_content.parse()?;
__brace_content.parse::()?;
let __ft: syn::Type = __brace_content.parse()?;
__f.push((__fn, __ft));
if __brace_content.peek(syn::Token![,]) {
__brace_content.parse::()?;
}
}
__f
};
let ret: syn::Type = _input.parse()?;
Ok((name, params, ret))
};
match __parser.parse2(input.clone()) {
Ok(v) => v,
Err(e) => return e.into_compile_error().into(),
}
};
let req_name = format_ident!("{}Request", name);
let res_name = format_ident!("{}Response", name);
let __spread_0: proc_macro2::TokenStream = params
.iter()
.map(|(__field_name, __field_ty)| {
quote::quote! {
pub # __field_name : # __field_ty,
}
})
.collect();
let __output = quote::quote! {
pub struct # req_name { # __spread_0 } pub struct # res_name { pub result : #
ret, }
};
__output.into()
}
```
---
## Quick start
```bash
# Install the CLI
cargo install misses
# Scaffold a new proc-macro crate (binary mode)
misses init my-macros
# Scaffold a library-friendly crate (generated code committed, no misses required downstream)
misses init --lib my-macros
# Compile a .mrs file to Rust
misses path/to/my_macro.mrs > src/generated.rs
misses path/to/my_macro.mrs src/generated.rs
```
---
## `misses init` — project scaffolding
`misses init` creates a ready-to-build proc-macro crate. Two modes are available depending on whether you're shipping a binary or a library.
### Binary mode (default)
```bash
misses init my-macros
```
Use this when you control the build environment (e.g. an application binary). The `.mrs` sources are compiled to Rust at build time via `build.rs`; the generated code lives in Cargo's `$OUT_DIR` and is **never committed**.
```
my-macros/
├── Cargo.toml # misses as a plain [build-dependencies]
├── build.rs # compiles src/macros/*.mrs → $OUT_DIR/*.rs
└── src/
├── lib.rs # include!(concat!(env!("OUT_DIR"), "/hello.rs"))
└── macros/
└── hello.mrs # your macro source (committed)
```
Users only need `misses` installed to build from source, which is fine for an app you control.
### Library mode (`--lib`)
```bash
misses init --lib my-macros
```
Use this when you're publishing a library crate. Downstream users of your crate should not be forced to install misses. The generated Rust code is committed to `generated/` and shipped on crates.io.
```
my-macros/
├── Cargo.toml # misses behind [features] misses-source = ["dep:misses"]
├── build.rs # no-op unless --features misses-source
├── generated/
│ └── hello.rs # pre-generated, committed to git
└── src/
├── lib.rs # include!(concat!(env!("CARGO_MANIFEST_DIR"), "/generated/hello.rs"))
└── macros/
└── hello.mrs # your macro source (committed)
```
When you modify a `.mrs` file, regenerate with:
```bash
cargo build --features misses-source
```
The `misses-source` feature makes `misses` an optional build-dependency and gates regeneration in `build.rs`. Downstream users build normally with no misses dependency.
---
## The `.mrs` syntax
A `.mrs` file contains one or more macro definitions:
```
macro macro_name! {
=> {