rodrimati1992

Ok, I'm gonna look at this today.

Having tried this locally, the error is caused by `halfbrown::Iter` deriving `Clone`, the solution is for it to manually implement `Clone` with no bounds on type parameters. [`halfbrown::Iter` requires Clone...

Loading multiple implementations of an interface can be done with: ```rust abi_stable::library::lib_header_from_path(&library_path) .and_then(|x| x.init_root_module::()) ``` I'm fine with PRs to ducument that it can be done this way.

:frowning: This would be two orders of magnitude more work than every other time that the compiler decided to break my code combined. The macros would also generate significantly more...

So is there an easy way to get the nightly compiler with these changes on x86-64 linux to try making those changes in abi_stable?

I wouldn't have as much of a problem with this change if it was easier to declare `const`ants that can access the generic parameters in the surrounding scope, the only...

I've downloaded the rustc from https://github.com/rust-lang/rust/pull/80243. Starting with the changes to `abi_stable` that are entirely internal, looks like making `abi_stable` compile with these changes to promotion would take multiple days,...

This comment is about the changes made to make abi_stable compile with [the pull request that disables promotion of all const fn calls](https://github.com/rust-lang/rust/pull/80243) So I worked on getting most of...

@RalfJung This is currently valid: ```rust const fn compute_u8() -> u8 { 10 } const FOO: &[u8] = { let number = compute_u8(); &[number, number] }; ``` If `rslice` macro...

What you quoted means that if you use `abi_stable`'s safe functions for loading dynamic libraries, you can't unload the dynamic library. You can still use data structures from the crate...