Imagine having a class named UserSystemCall.
Each subclass targets a method (lazily, so it is Class+ selector rather than a CompiledMethod), an action to use as replacement (or not), a rule for enable or disable, and a groupName.
Add a new UI (like SeekerConfig) to enable or disable these methods.
SystemCalls are not undoable, and the debugger will not query inside them. In turn, they act as if it is only one instruction, and they are interpreted faster. It could be useful to enable
Possible use cases:
Treat announcements as system calls.
Ignore drawing or layout calls in general (there are a lot!).
Imagine having a class named UserSystemCall. Each subclass targets a method (lazily, so it is Class+ selector rather than a CompiledMethod), an action to use as replacement (or not), a rule for enable or disable, and a groupName. Add a new UI (like SeekerConfig) to enable or disable these methods. SystemCalls are not undoable, and the debugger will not query inside them. In turn, they act as if it is only one instruction, and they are interpreted faster. It could be useful to enable Possible use cases: