Casper
Casper
The PR looks great so far! Separating the keys and values into separate tables isn't just good for packing, it's also great for cache pressure since the values of all...
Hi, thanks for taking your time to using my library! There is a type exposed to work with both 32-bit and 64-bit Pe types: [`Wrap`](https://docs.rs/pelite/0.9.0/pelite/enum.Wrap.html) which is aliased as [`PeFile`](https://docs.rs/pelite/0.9.0/pelite/type.PeFile.html)....
Unfortunately this use case isn't really supported due to pelite using shared borrows everywhere. The best alternative is to gather a set of 'todo' modifications and after destroying all pelite...
Hi, sorry about the bad experience... I think the problem is most likely related to intptr crate having a feature you have to enable to make it implement Pod (which...
Does the same problem not happen with the `#[inline(never)]` approach? There should be a ton of `mov rax, OFFSET; retn` funcs which you can easily enumerate as well.
That's unfortunate. The design of pelite demands that everything is aligned so that I can give references to the underlying data instead of making copies. This makes pelite a 'zero...
This is interesting and has been on my mind but I couldn't get the code right to my satisfaction. In the meantime I did work on a JS API (powered...
Hello, It seems like the bswap instruction bytes are marked as invalid in both x86 and x64 tables for some reason. That should be a simple fix. I can't find...
Thanks! I'll take a look at it later.
Should be fixed by @mrsteyk at #60