-
Is it possible to implement lalrpop in proc macro so that it doesn't require a build script?
-
wasmer-ruby wrote some proc proc macros - it would be good if these were integrated in rutie - haven't brought it up in the wasmer project yet.
https://github.com/wasmerio/wasmer-ruby/pull/48
-
The `syn` crate has an unsafe code, according to the `cargo-geiger`, but it will be used only during compilation (afaik). It doesn't affect the resulting binary.
-
## Feature Request
It's common to want to use tracing in tests because who doesn't want to use tracing everywhere. Right now this adds an extra bit of boiler plate to every test. Also it's not wide…
yaahc updated
4 years ago
-
### Problem
With `resolver = "2"`, and a workspace with a proc-macro, duplicates of a shared dependency are not displayed in `cargo tree` in some situations.
### Steps
The following cargo test demo…
-
The library I'm working on, has the requirement of being able to be used by rust and non-rust users.
I didn't like the idea of creating a separate crate in the project just as a wrapper for my main…
-
Currently we make no real effort to inform users of parse errors in procedural macro output: https://github.com/rust-lang/rust/blob/9c15de4fd59bee290848b5443c7e194fd5afb02c/src/libsyntax_ext/deriving/…
-
I'm currently working on a pr that allows proc_macro to run inside webassembly by implementing a `proc_macro::bridge::Server` that forwards all the calls over ffi to the real macro. (I already got the…
-
I'm building a hello world generated by cargo, using this .cargo/config:
```toml
[target.x86_64-pc-windows-msvc]
linker = "lld-link.exe"
rustflags = ["-Clinker=lld-link", "-Clinker-plugin-lto"]
…
-
### Steps to reproduce
```
git clone https://gitlab.torproject.org/Diziet/arti -b report-inference-failure
cd arti
cargo +nightly check --locked -p tor-socksproto --all-features --all-targe…