Jeff Burdges
@zjp-CN > Do you indicate tags work bad on nested unsafe calls? I've no opinion on this RFC, or the previous one, or when one should create some static analysis...
I always use this crate myself now that its maintained again, so I won't clutter this thread, but I've posted https://github.com/dalek-cryptography/curve25519-dalek/issues/812 for discussion about converting to other's field representations
We could avoid Rule 1 by building the vtable lookup table externally in `./target`, no? As `&'static [(TypeId, TraitVTable)]` is a nasty lookup, https://internals.rust-lang.org/t/casting-families-for-fast-dynamic-trait-object-casts-and-multi-trait-objects/12195 proposed defining fresh indices for each...
Appears [intertrait](https://crates.io/crates/intertrait) already provides a much cleaner solution, by using the [linkme](https://crates.io/crates/linkme). At present linkme needs linker support, but one could bypass the linker, using only `#[no_mangle]` and procmacros. Also,...
Interesting thanks. Appears 4 years since their last version, and the owning blockchain has no updates since May 2023, so bitrot. It nevertheless shows that rule 1 maybe excessively restrictive....
Yes, but only for types defined downstream of both traits, by Rule 1. If you have a &dyn A coming from a &u64 under the hood, then you cannot cast...
At present dalek is single threaded, but maybe multi-threaded CPU based MSMs make sense here? At https://zka.lc/ try large and small MSM for curve25519-dalek and arkworks' curve25519. Arkworks is much...