David Tolnay
David Tolnay
Currently we disallow any user-defined type name that collides with one of the builtin type names. ```console error[cxxbridge]: reserved name ┌─ src/main.rs:3:12 │ 3 │ struct UniquePtr { broken: bool...
Imagining something like: ```rust #[cxx::bridge] mod ffi { #[dynamic_load] extern "C++" { /* as normal */ fn demo(s: &str) -> u8; } } fn main() -> Result { let ffi...
Currently if we have: ```rust mod ffi { extern "C++" { fn f(callback: fn()); } } ``` then Rust can call it as: ```rust ffi::f(|| { do_something(); }); ``` but...
The pure Rust implementation is good as a default, but it would be amazing to also provide: ```toml [dependencies] gflags = { version = "0.N", features = ["interop"] } ```...
Something like: ```rust gflags::define! { -f, --file ... } ``` where it would accept the same flag multiple times (`-f path1 -f path2 -f path3`) and expose them all in...
The poor interaction between method bodies and handling of relative paths in `use` statements in Rust makes this extremely challenging or (I currently believe) impossible to support. Doesn't hurt to...
It would be helpful to have a copy of the "How to get started" readme section as a fully laid out [examples](https://doc.rust-lang.org/cargo/reference/manifest.html#examples) directory where someone could just drop in and...
It has been deprecated: [announcement](https://users.rust-lang.org/t/deprecation-of-rustc-serialize/10485?u=dtolnay).
I see that this was discussed previously in #10 and #30 but as far as I can tell, it was never coherently explained why cargo-update needs to do this differently....
```rust use anyhow::Error; use fehler::throws; #[throws] fn f() {} fn g() {} fn main() {} ``` ```console warning: function is never used: `g` --> src/main.rs:7:4 | 7 | fn g()...