iximeow
iximeow
> I don't know why is wasmtime not allowing hosts to hold simultaneously `share borrow` and `mut borrow` pointer of `guest memory`. I feel like this can be relaxed like...
this seems like good advice for any implementors of `yaxpeax-arch`, yeah. it might also make sense to re-export `num_traits::Zero` or at least provide functions like `zero()` and `one()` on `Address`...
1.64 is out! grats on landing the lints! i don't think there've been any no-std pull requests, but [some commits](https://github.com/iximeow/yaxpeax-x86/commit/2097524c851b15e89091fd3775817a06f0eeae4f#diff-57b8a7f149836741dfbeaa669e680cc396d897b6cde14430c9628eac89dadc9d) if that's what you're thinking? in that case it was...
i agree, github issues don't lend themselves to usage/support or even design conversation very much. elsewhere i end up using github issues (or comments therein) as a summary of a...
gitter does seem to be like the least irritating option, and does bridge to matrix well enough. so, now there's https://gitter.im/yaxpeax/yaxpeax#, or `#yaxpeax_yaxpeax:gitter.im` to other matrix clients. next up is...
agreed on all counts! [`yaxpeax_core`](https://github.com/iximeow/yaxpeax-core/blob/87786db784bff488ad374b751b1ccc1bd75036eb/src/data/mod.rs#L18-L45) has a pretty unsatisfactory interface for this that i'd never gotten happy enough with to move over to `arch`, but i definitely agree that "this...
> why would wasmparser ever need anything within libstd that isn't in liballoc or libcore? `std::error::Error` is in fact in std, not a re-export out of libcore or liballoc. as...
hey that's great! that you can use the crate to disassemble the crashing instruction, anyway :) the short answer is, unfortunately, there's no missing feature in `yaxpeax-x86` to get access...
hmm, i was thinking of a bit of a different approach: as you've noted, `Operand` and `Opcode` generally are very similar, so i think we could actually replace explicitly writing...
ah! i was wondering if you'd made progress on this or put it aside. is there already a proc macro for `superset` or would you have to write that too?...