Travis Finkenauer

@SWW13 Thanks for the pull-request! This is great work. If you have any questions related to review comments or capstone, feel free to reach out.

Thanks for filing the issue! I have thought about doing something like this before. I did not do this originally because I wanted to support "dynamic architecture". I like your...

There's not need to make a separate submodule--just put new code in whatever module makes sense. It's always easy to move it around anyway.

Sorry for the late reply. The Rust types are "bespoke" and written by hand. :sweat_smile: If you are interested in contributing the feature, take a look at `RegAccessType` and the...

Fixed FreeBSD w/ #105

@froydnj Thanks for your bug report! I've considered adding this feature, but, depending on the implementation, it's a lot of work. We could have a feature `support_all_archs` that depends on...

Thanks for filing the issue! I see what you are saying, `Insn::id()` returns an `InsnId`, which just contains an integer value. However, the architecture-specific instruction enums like `X86Insn` cannot be...

Also, to do what you wanted, with the current `capstone-rs`, you would do something like: ~~~rust fn is_valid_ret(insn: Insn) -> bool { match insn.id().0 { x if x == arch::x86::X86Insn::X86_INS_RET...

Thanks for filing the issue! As you pointed out, this will mostly be solved once we fix #68. It seems like you probably have the right idea that we should...

@vn-ki I did not make any plans to implement this myself. I would greatly appreciate help with this! Would you like to open a PR? I would be happy to...