2020-04-01 00:11:26 -05:00
|
|
|
//! RA Proc Macro Server
|
|
|
|
//!
|
|
|
|
//! This library is able to call compiled Rust custom derive dynamic libraries on arbitrary code.
|
2021-06-13 23:57:10 -05:00
|
|
|
//! The general idea here is based on <https://github.com/fedochet/rust-proc-macro-expander>.
|
2020-04-01 00:11:26 -05:00
|
|
|
//!
|
2020-04-20 13:26:10 -05:00
|
|
|
//! But we adapt it to better fit RA needs:
|
2020-04-01 00:11:26 -05:00
|
|
|
//!
|
2020-08-12 09:46:20 -05:00
|
|
|
//! * We use `tt` for proc-macro `TokenStream` server, it is easier to manipulate and interact with
|
2020-04-20 13:26:10 -05:00
|
|
|
//! RA than `proc-macro2` token stream.
|
2020-04-01 00:11:26 -05:00
|
|
|
//! * By **copying** the whole rustc `lib_proc_macro` code, we are able to build this with `stable`
|
2020-08-13 05:07:28 -05:00
|
|
|
//! rustc rather than `unstable`. (Although in general ABI compatibility is still an issue)…
|
2022-07-20 07:59:42 -05:00
|
|
|
|
|
|
|
#![warn(rust_2018_idioms, unused_lifetimes, semicolon_in_expressions_from_macros)]
|
2022-07-20 11:27:58 -05:00
|
|
|
#![cfg_attr(
|
|
|
|
feature = "sysroot-abi",
|
|
|
|
feature(proc_macro_internals, proc_macro_diagnostic, proc_macro_span)
|
|
|
|
)]
|
2020-11-02 06:13:32 -06:00
|
|
|
#![allow(unreachable_pub)]
|
2020-04-01 00:11:26 -05:00
|
|
|
|
2020-04-04 03:09:36 -05:00
|
|
|
mod dylib;
|
2021-07-12 09:47:47 -05:00
|
|
|
mod abis;
|
|
|
|
|
2022-10-11 02:37:35 -05:00
|
|
|
pub mod cli;
|
|
|
|
|
2020-04-23 21:23:01 -05:00
|
|
|
use std::{
|
|
|
|
collections::{hash_map::Entry, HashMap},
|
2022-01-27 12:34:18 -06:00
|
|
|
env,
|
|
|
|
ffi::OsString,
|
|
|
|
fs,
|
2020-04-23 21:23:01 -05:00
|
|
|
path::{Path, PathBuf},
|
2022-08-30 06:51:24 -05:00
|
|
|
thread,
|
2020-04-24 23:30:28 -05:00
|
|
|
time::SystemTime,
|
2020-04-23 21:23:01 -05:00
|
|
|
};
|
|
|
|
|
internal: cleanup proc macro server error handlig
When dealing with proc macros, there are two very different kinds of
errors:
* first, usual errors of "proc macro panicked on this particular input"
* second, the proc macro server might day if the user, eg, kills it
First kind of errors are expected and are a normal output, while the
second kind are genuine IO-errors.
For this reason, we use a curious nested result here: `Result<Result<T,
E1>, E2>` pattern, which is 100% inspired by http://sled.rs/errors.html
2021-08-31 11:01:39 -05:00
|
|
|
use proc_macro_api::{
|
|
|
|
msg::{ExpandMacro, FlatTree, PanicMessage},
|
|
|
|
ProcMacroKind,
|
|
|
|
};
|
|
|
|
|
2020-04-23 21:23:01 -05:00
|
|
|
#[derive(Default)]
|
|
|
|
pub(crate) struct ProcMacroSrv {
|
2020-04-24 23:30:28 -05:00
|
|
|
expanders: HashMap<(PathBuf, SystemTime), dylib::Expander>,
|
2020-04-23 21:23:01 -05:00
|
|
|
}
|
2020-04-04 03:10:45 -05:00
|
|
|
|
2022-08-02 01:05:16 -05:00
|
|
|
const EXPANDER_STACK_SIZE: usize = 8 * 1024 * 1024;
|
|
|
|
|
2020-04-23 21:23:01 -05:00
|
|
|
impl ProcMacroSrv {
|
internal: cleanup proc macro server error handlig
When dealing with proc macros, there are two very different kinds of
errors:
* first, usual errors of "proc macro panicked on this particular input"
* second, the proc macro server might day if the user, eg, kills it
First kind of errors are expected and are a normal output, while the
second kind are genuine IO-errors.
For this reason, we use a curious nested result here: `Result<Result<T,
E1>, E2>` pattern, which is 100% inspired by http://sled.rs/errors.html
2021-08-31 11:01:39 -05:00
|
|
|
pub fn expand(&mut self, task: ExpandMacro) -> Result<FlatTree, PanicMessage> {
|
|
|
|
let expander = self.expander(task.lib.as_ref()).map_err(|err| {
|
|
|
|
debug_assert!(false, "should list macros before asking to expand");
|
2023-01-09 12:36:22 -06:00
|
|
|
PanicMessage(format!("failed to load macro: {err}"))
|
internal: cleanup proc macro server error handlig
When dealing with proc macros, there are two very different kinds of
errors:
* first, usual errors of "proc macro panicked on this particular input"
* second, the proc macro server might day if the user, eg, kills it
First kind of errors are expected and are a normal output, while the
second kind are genuine IO-errors.
For this reason, we use a curious nested result here: `Result<Result<T,
E1>, E2>` pattern, which is 100% inspired by http://sled.rs/errors.html
2021-08-31 11:01:39 -05:00
|
|
|
})?;
|
2020-12-11 07:57:50 -06:00
|
|
|
|
2022-01-27 12:34:18 -06:00
|
|
|
let prev_env = EnvSnapshot::new();
|
2020-12-11 07:57:50 -06:00
|
|
|
for (k, v) in &task.env {
|
|
|
|
env::set_var(k, v);
|
|
|
|
}
|
2022-01-27 06:54:06 -06:00
|
|
|
let prev_working_dir = match task.current_dir {
|
|
|
|
Some(dir) => {
|
|
|
|
let prev_working_dir = std::env::current_dir().ok();
|
|
|
|
if let Err(err) = std::env::set_current_dir(&dir) {
|
2023-01-09 12:36:22 -06:00
|
|
|
eprintln!("Failed to set the current working dir to {dir}. Error: {err:?}")
|
2022-01-27 06:54:06 -06:00
|
|
|
}
|
|
|
|
prev_working_dir
|
|
|
|
}
|
|
|
|
None => None,
|
|
|
|
};
|
2020-12-11 07:57:50 -06:00
|
|
|
|
2021-08-28 12:36:41 -05:00
|
|
|
let macro_body = task.macro_body.to_subtree();
|
|
|
|
let attributes = task.attributes.map(|it| it.to_subtree());
|
2022-08-30 06:51:24 -05:00
|
|
|
let result = thread::scope(|s| {
|
|
|
|
let thread = thread::Builder::new()
|
2022-08-02 01:05:16 -05:00
|
|
|
.stack_size(EXPANDER_STACK_SIZE)
|
|
|
|
.name(task.macro_name.clone())
|
2022-08-30 06:51:24 -05:00
|
|
|
.spawn_scoped(s, || {
|
2022-07-21 14:35:15 -05:00
|
|
|
expander
|
|
|
|
.expand(&task.macro_name, ¯o_body, attributes.as_ref())
|
|
|
|
.map(|it| FlatTree::new(&it))
|
2022-08-30 06:51:24 -05:00
|
|
|
});
|
|
|
|
let res = match thread {
|
2022-08-02 01:05:16 -05:00
|
|
|
Ok(handle) => handle.join(),
|
|
|
|
Err(e) => std::panic::resume_unwind(Box::new(e)),
|
|
|
|
};
|
2022-07-21 14:35:15 -05:00
|
|
|
|
|
|
|
match res {
|
|
|
|
Ok(res) => res,
|
|
|
|
Err(e) => std::panic::resume_unwind(e),
|
|
|
|
}
|
|
|
|
});
|
2020-12-11 07:57:50 -06:00
|
|
|
|
2022-01-27 12:34:18 -06:00
|
|
|
prev_env.rollback();
|
|
|
|
|
2022-01-27 06:54:06 -06:00
|
|
|
if let Some(dir) = prev_working_dir {
|
|
|
|
if let Err(err) = std::env::set_current_dir(&dir) {
|
|
|
|
eprintln!(
|
|
|
|
"Failed to set the current working dir to {}. Error: {:?}",
|
|
|
|
dir.display(),
|
|
|
|
err
|
|
|
|
)
|
|
|
|
}
|
|
|
|
}
|
2020-12-11 07:57:50 -06:00
|
|
|
|
internal: cleanup proc macro server error handlig
When dealing with proc macros, there are two very different kinds of
errors:
* first, usual errors of "proc macro panicked on this particular input"
* second, the proc macro server might day if the user, eg, kills it
First kind of errors are expected and are a normal output, while the
second kind are genuine IO-errors.
For this reason, we use a curious nested result here: `Result<Result<T,
E1>, E2>` pattern, which is 100% inspired by http://sled.rs/errors.html
2021-08-31 11:01:39 -05:00
|
|
|
result.map_err(PanicMessage)
|
2020-04-04 03:10:45 -05:00
|
|
|
}
|
|
|
|
|
internal: cleanup proc macro server error handlig
When dealing with proc macros, there are two very different kinds of
errors:
* first, usual errors of "proc macro panicked on this particular input"
* second, the proc macro server might day if the user, eg, kills it
First kind of errors are expected and are a normal output, while the
second kind are genuine IO-errors.
For this reason, we use a curious nested result here: `Result<Result<T,
E1>, E2>` pattern, which is 100% inspired by http://sled.rs/errors.html
2021-08-31 11:01:39 -05:00
|
|
|
pub(crate) fn list_macros(
|
|
|
|
&mut self,
|
|
|
|
dylib_path: &Path,
|
|
|
|
) -> Result<Vec<(String, ProcMacroKind)>, String> {
|
|
|
|
let expander = self.expander(dylib_path)?;
|
|
|
|
Ok(expander.list_macros())
|
2020-04-23 21:23:01 -05:00
|
|
|
}
|
2020-04-20 13:26:10 -05:00
|
|
|
|
2020-04-23 21:23:01 -05:00
|
|
|
fn expander(&mut self, path: &Path) -> Result<&dylib::Expander, String> {
|
2023-01-09 12:36:22 -06:00
|
|
|
let time = fs::metadata(path)
|
|
|
|
.and_then(|it| it.modified())
|
|
|
|
.map_err(|err| format!("Failed to get file metadata for {}: {err}", path.display()))?;
|
2020-04-24 23:30:28 -05:00
|
|
|
|
|
|
|
Ok(match self.expanders.entry((path.to_path_buf(), time)) {
|
2023-01-09 12:36:22 -06:00
|
|
|
Entry::Vacant(v) => {
|
|
|
|
v.insert(dylib::Expander::new(path).map_err(|err| {
|
|
|
|
format!("Cannot create expander for {}: {err}", path.display())
|
|
|
|
})?)
|
|
|
|
}
|
2020-04-23 21:23:01 -05:00
|
|
|
Entry::Occupied(e) => e.into_mut(),
|
|
|
|
})
|
|
|
|
}
|
2020-04-01 00:11:26 -05:00
|
|
|
}
|
2020-04-09 12:43:47 -05:00
|
|
|
|
2022-01-27 12:34:18 -06:00
|
|
|
struct EnvSnapshot {
|
|
|
|
vars: HashMap<OsString, OsString>,
|
|
|
|
}
|
|
|
|
|
|
|
|
impl EnvSnapshot {
|
|
|
|
fn new() -> EnvSnapshot {
|
|
|
|
EnvSnapshot { vars: env::vars_os().collect() }
|
|
|
|
}
|
|
|
|
|
|
|
|
fn rollback(self) {
|
|
|
|
let mut old_vars = self.vars;
|
|
|
|
for (name, value) in env::vars_os() {
|
|
|
|
let old_value = old_vars.remove(&name);
|
|
|
|
if old_value != Some(value) {
|
|
|
|
match old_value {
|
|
|
|
None => env::remove_var(name),
|
|
|
|
Some(old_value) => env::set_var(name, old_value),
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
for (name, old_value) in old_vars {
|
|
|
|
env::set_var(name, old_value)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2022-10-11 02:37:35 -05:00
|
|
|
#[cfg(all(feature = "sysroot-abi", test))]
|
|
|
|
mod tests;
|
2020-04-16 08:13:57 -05:00
|
|
|
|
2020-04-09 12:43:47 -05:00
|
|
|
#[cfg(test)]
|
2022-10-11 02:37:35 -05:00
|
|
|
pub fn proc_macro_test_dylib_path() -> std::path::PathBuf {
|
|
|
|
proc_macro_test::PROC_MACRO_TEST_LOCATION.into()
|
|
|
|
}
|