Strict pointer provenance
Much of the current API violates strict provenance, for example syscall::call::fmap
returning a usize
instead of a pointer. Changing this would obviously be a breaking change, but good to keep in mind for the next semver-breaking version bump (i.e. 0.4.0
).