Closed shepmaster closed 4 years ago
Released in 0.2.4
.
Relatedly, is there a reason for the PhantomData<()>
in DisableInterrupts
?
That’s probably an artifact of me being overzealous. The type needs to contain something to prevent it from being instantiated without calling the new
function. That could probably be a simple empty tuple. The PhantomData
is only used as a belt-and-suspenders technique to make sure that it doesn’t take up any size.
It never makes sense to call a function for these two instructions.
Additionally, I use this at system boot time to configure the stack pointer itself. If this becomes a function call, then everything is broken!