Willi Ballenthin

- format - lint - build

- [mimalloc](https://github.com/microsoft/mimalloc) - [scudo](https://github.com/google/rust-scudo)

dis: zydis guarantees visible/explicit operands to be first

3

referenced here but im not sure where else: https://github.com/zyantific/zydis/issues/189

https://iximiuz.com/en/posts/rust-writing-parsers-with-nom/

rather than computing addresses ourselves. might as well rely on well-tested zydis for this.

function padding background research

1

- https://stackoverflow.com/questions/25545470/long-multi-byte-nops-commonly-understood-macros-or-other-notation - https://github.com/intelxed/xed/blob/b53f33e44dd2e5fb2e63f9c0e35c65b72c933dae/src/enc/xed-encode.c#L460 - https://gist.github.com/stevemk14ebr/d117e8d0fd1432fb2a92354a034ce5b9 - https://reverseengineering.stackexchange.com/questions/4084/why-ther-are-some-many-padding-leading-nop-instructions-in-my-binary-code - https://stackoverflow.com/questions/7912464/why-does-gcc-pad-functions-with-nops - https://reviews.llvm.org/D70157 -https://www.reddit.com/r/programming/comments/8vha0o/two_little_nuggets_about_nop_instruction/

- https://depth-first.com/articles/2020/06/22/returning-rust-iterators/ - https://stackoverflow.com/questions/27535289/what-is-the-correct-way-to-return-an-iterator-or-any-other-trait