Bijan Kazemi-Shirkadeh

I believe I finished it, but there were some bits @sriemer didn't like so I held off on opening a PR. You can have a look on my [code-cleanup](/bkazemi/scanmem/tree/code-cleanup) branch.

Yeah, in retrospect I think the best way to go about it is in individual parts. I have the typo fixes. I'll open a new branch.

This could be done, but you'd have to redo the search due to the possibility of the matches being moved around in memory. If I remember correctly, someone has requested...

https://github.com/scanmem/scanmem/issues/341 same question right? Personally I like the idea, if you have enough memory, it'd be convenient. We could add an option to automatically prune the addresses that don't match...

Sounds good to me. Perhaps we could check memory usage and show a warning if the user starts using enough RAM to slow down their system; With today's RAM, only...

I personally don't have any GC patches presently, so scratch me off. However, it might be a good idea to decide on the One True Style (tm) for python code...

Hmm, maybe it wouldn't be a bad idea to add a kind-of set element "binding" value to handle `elem=...`. We could make it an optional flag to pass to `parse_uintset`.

Ah, I see. That is definitely a better way to go. It'd keep the set 'datatype' pure.

I'll go ahead and assign myself. I could get this into `v0.17`, if you'd like.

I have this done in O(n^2) (as it was). If this is too slow, it can be changed. I set over 200,000 elements pretty quickly, however.