Christian Poveda Ruiz
Christian Poveda Ruiz
> Regardless of how this c code was generated. We would need to compile the c code first and then "re-run" bindgen over it respecting all the `BindgenOptions` that were...
> > Regardless of how this c code was generated. We would need to compile the c code first and then "re-run" bindgen > > Why does the C-code need...
Ok I have a very hacky PoC [here](https://github.com/ferrous-systems/rust-bindgen/tree/emit-c-code). The pipeline is be the following: - Save the builder original state in case we need to rerun it later (this is...
Hi @kulp thanks for you answer :) > An incremental approach, using relatively small, reversible changes, is a strongly favorable thing for me. Yeah I think this is definitely possible,...
it would be definitely possible to use the output of `codegen::codegen` and doing `parse_quote!(mod something { #( #items )* })`, and then taking the contents of the module but it...
That being said, moving to `syn` completely could be used to do some of these fixes "earlier" in code generation. But for the two issues I mentioned above, we can...
Given that https://github.com/rust-lang/rust-bindgen/pull/2254 is close to being merged I'm marking this as solved
once https://github.com/iotaledger/bee/pull/933 is merged I can open another PR that doesn't use `std::collections` in `no_std` environments to make `bee-message` fully `no_std`
librocksdb-sys requires a rocksdb version compatible with 6.22.1 and Ubuntu repos only provide 6.11.4 We'd have to figure out if that is enough or if we can download the right...
Is this fixed via #2145?