Open
Description
#49219 introduces proc_macro::bridge::server::{ExecutionStrategy,SameThread,CrossThread}
.
SameThread
had to be used because CrossThread
was a significant performance regression.
Ideally, we'd use CrossThread
, which spawns a thread for each invocation, to prevent (and discourage) proc macros from using TLS for state between invocations.
But we'd have to figure out how to make it not regress performance too much, if at all possible.
(it could be the use of channels, which are overkill since they never have more than one value)
cc @dtolnay @alexcrichton @petrochenkov
(TODO: update with regressions, if any, after the cross-thread crater run finishes on #49219)