refactor side branch

[dword64]

you know, if you know

[dword64]

Just leaving this here. As discussed earlier, we're going to implement flags so that the user can override them.

1. Global Default

• Set once: symbolic or concrete.

2. Section-Based Rules

• .data → symbolic
• .text → concrete (unless overridden)
• Use ELF/PE headers to seed these defaults (RWX flags).

3. Range Overrides

• User defined: "from 0x401000 to 0x402000 → concrete"
• Great for runtime mapped config blobs, custom packers.

4. Runtime Hooking / Dynamic Paging

• Callback or event system to change policies at runtime:

on_protect_change(addr, new_flags) {
    mem_policy.update(addr, page_flags_to_mode(new_flags));
}

Since this is a hot function (we're reading bytes while disassembling), introducing a branch could impact performance. If possible, we should use templates to handle the logic at compile time, avoiding runtime branches

[NaC-L]

todo: fix passes

lgtm