Saúl Cabrera (Apr 27 2022 at 12:06): Saúl Cabrera (Apr 27 2022 at 12:06):Hey! I have a small question around the API for epoch based interruption: is there a particular reason why the EpochDeadlineError isn't publicly exposed? We are currently migrating to epoch based interruption from the previous approach in which the API returned a TrapCode::Interrupt to signal an interruption in execution. Would it make sense to expose it? Or perhaps I'm missing something and there's an equivalent way to TrapCode::Interrupt to determine when the execution was interrupted?
Alex Crichton (Apr 27 2022 at 13:40):Exposing either the error or a trap code makes sense to me, it's not necessarily intentional it's private we just do that by default to be conservative
Saúl Cabrera (May 02 2022 at 15:00):I meant to get to this earlier, sorry about that. All that makes sense to me, thanks for the context @Alex Crichton ! I can give this one a try if no one else is working on it.
Alex Crichton (May 02 2022 at 15:00):Sounds good to me, feel free!
Last updated: Nov 22 2024 at 16:03 UTC