Comments (2)
Thanks for reporting this, this is indeed a limitation of safer-ffi's design: we can't really know how to stringify the generic parameters (in the non-opaque case, we get away thanks to the recursive ReprC
obligation on the generic parameters, which is the one providing the stringified sub name (the short_name
, for those curious about the internals)).
A way to palliate the issue, which I've used in some cases, is to use the undocumented1 rename feature of ReprC::opaque
:
#[derive_ReprC]
#[ReprC::opaque(format!(
"Foo_{}",
::std::any::type_name::<T>()
.splitn(2, "<")
.next().unwrap()
.rsplitn(2, ":")
.next().unwrap()
))]
struct Foo<T> { /* … */ }
it's not pretty, but at the time I did not want to provide this as a default implementation, thence hiding nested collisions.
In the near future
I now think that such implementation, especially if recursing into the generic parameters, is not that bad, and definitely better than just disregarding the type parameters in the name.
Thus, as part of the incoming cleanup and refactoring of safer-ffi, such an implementation will be available by default, thence fixing this very issue 🙂
Footnotes
-
an oversight, I guess ↩
from safer_ffi.
This was fixed as of #97 (to be released to crates.io)
from safer_ffi.
Related Issues (20)
- Specifying `[[bin]]` with required features should be a required instruction HOT 1
- Quickstart `crate-type` `lib` seems documented too optional
- Trivial example requires `python-headers` feature to build HOT 2
- No `DOXYGEN` def yields incorrect enum definition HOT 1
- Missing `Clone` impl for `repr_c::Box` (and friends?)
- VS code complains non snake case
- Generated Clone implementation triggers clippy lint about being incorrect for a Copy type HOT 4
- Allow disabling dependency on `inventory v0.1` HOT 2
- Macro ambiguity on nightly: `std::cfg_match` vs `crate::utils::macros::cfg_match` HOT 1
- Conditional proc-macros HOT 2
- How does `safer_ffi` avoid aliasing rule problem? HOT 3
- Compatibility with C++ vector HOT 2
- Handle non-panic Tokio task termination
- no_libc feature?
- C# headers are `public`, when `internal` visibility most likely suffices
- No tag or release for v0.1.5 HOT 1
- Feature Request: Generate rust fn and struct declarations instead of C headers HOT 1
- Python example? HOT 1
- Feature request: serde Serialize and Deserialize support for repr_c::String and repr_c::Vec
- Inconsistent MSRV user guide HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from safer_ffi.