File: mod.rs

package info (click to toggle)
rust-bindgen 0.72.1-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,412 kB
  • sloc: makefile: 8
file content (57 lines) | stat: -rw-r--r-- 1,510 bytes parent folder | download | duplicates (21)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
use proc_macro2::TokenStream;
use quote::ToTokens;
use syn::{parse2, File};

use crate::BindgenOptions;

mod merge_extern_blocks;
mod sort_semantically;

use merge_extern_blocks::merge_extern_blocks;
use sort_semantically::sort_semantically;

struct PostProcessingPass {
    should_run: fn(&BindgenOptions) -> bool,
    run: fn(&mut File),
}

// TODO: This can be a const fn when mutable references are allowed in const
// context.
macro_rules! pass {
    ($pass:ident) => {
        PostProcessingPass {
            should_run: |options| options.$pass,
            run: |file| $pass(file),
        }
    };
}

const PASSES: &[PostProcessingPass] =
    &[pass!(merge_extern_blocks), pass!(sort_semantically)];

pub(crate) fn postprocessing(
    items: Vec<TokenStream>,
    options: &BindgenOptions,
) -> TokenStream {
    let items = items.into_iter().collect();
    let require_syn = PASSES.iter().any(|pass| (pass.should_run)(options));

    if !require_syn {
        return items;
    }

    // This syn business is a hack, for now. This means that we are re-parsing already
    // generated code using `syn` (as opposed to `quote`) because `syn` provides us more
    // control over the elements.
    // The `unwrap` here is deliberate because bindgen should generate valid rust items at all
    // times.
    let mut file = parse2::<File>(items).unwrap();

    for pass in PASSES {
        if (pass.should_run)(options) {
            (pass.run)(&mut file);
        }
    }

    file.into_token_stream()
}