RzMemory for mapped IO interactions.

[wargio]

Your checklist for this pull request

• I've read the guidelines for contributing to this repository.
• I made sure to follow the project's coding style.
• I've documented every RZ_API function and struct this PR changes.
• I've added tests that prove my changes are effective (required for changes to RZ_API).
• I've updated the Rizin book with the relevant information (if needed).
• I've used AI tools to generate fully or partially these code changes and I'm sure the changes are not copyrighted by somebody else.

Detailed description

Should replace the whole RzIO layer and most of the RzIO handlers should be translated in RzBuffer equivalents

[Rot127]

hidden means: region is completely covered by another memory region?

[wargio]

yes

[Rot127]

One requirement I would have is for the behavior of reading. It should be configurable. By passing a flag or something.

enum {
  FIXED_BLOCK, ///< Reads the requested number of bytes. If it reads less than the request number of bytes, the read fails.
  UP_TO, ///< Reads up to the number of requested bytes. If it reads less than that, the read still succeeds.
  AT_LEAST, ///< The number of requested bytes is the minimum bytes which must be read. Otherwise the read fails.
} RzMemReadBehvior;

I am so so annoyed about hour inconsistent and complicated reading behavior.
Having control over it would be a blessing.

[Rot127]

Also, keep in mind that RzBuffer can't properly handle addresses above ST64_MAX.

[wargio]

Also, keep in mind that RzBuffer can't properly handle addresses above ST64_MAX.

i forgot about that!

[wargio]

One requirement I would have is for the behavior of reading. It should be configurable

i can replace the bool sparse arg with this enum.

[wargio]

isn't FIXED_BLOCK and AT_LEAST the same? because otherwise i would need to define an extra variable to say min x bytes and max x bytes

[Rot127]

isn't FIXED_BLOCK and AT_LEAST the same? because otherwise i would need to define an extra variable to say min x bytes and max x bytes

Ah yes, sorry. It was late while writing this.