-
In a proc-macro that generates a macro_rules macro that triggers lints like `unsafe_op_in_unsafe_fn`, or `unsafe_attr_outside_unsafe`, the suggestion ends up suggesting that the `unsafe` should go aro…
-
Please check out https://rustsec.org/advisories/RUSTSEC-2024-0370
It advises using one of the following crates instead:
* [manyhow](https://crates.io/crates/manyhow)
* [proc-macro-error2](https…
-
How would you go about using it in combination with proc macros? Is there anything to watch out for/special you need to do?
For example, this project structure:
```
my_crate/
| - src/
| | - ...…
-
This is a tracking issue for making `proc_macro` usable in all crates, not just those with crate type `proc-macro`. Advantages:
- Simplified testing of procedural macros
- Examples in the [API docs](…
-
We should NOT migrate whole state on db swap, but it leads to fresh diagnostics calculation every 5 minutes, also sending requests again and that is not acceptable
-
Feature gate: `#![feature(proc_macro_totokens)]`
This is a tracking issue for adding a `ToTokens` trait in `proc_macro`, which can then be used in `proc_macro::quote!`. See [the ACP](https://github.c…
-
Would you be interested in a PR to more accurately pin point error locations when using the derive macro?
shahn updated
4 weeks ago
-
https://rustsec.org/advisories/RUSTSEC-2024-0370.html
-
### Problem
When testing proc-macros with `-Zbuild-std`, the binary under test fails to load the standard library (at least on macOS):
```console
Running unittests src/lib.rs (target/debug/deps…
-
### Describe the improvement
It seems that the proc_macro_error crate is [flagged as unmaintained](https://rustsec.org/advisories/RUSTSEC-2024-0370).
That is used on shuttle_codegen.
Is there a…