Why does mlua hold a lua state lock across an entire resume call #616

Been trying to debug a strange locking issue in send mode and found that mlua seems to hold a lock around lua across en entire Thread::resume call. Won't this lead to issues if another thread tries to perform operations on the lua VM while in a lua thread resume [aka, shouldnt mlua release the lock before the resume and then relock or am I not seeing it correctly]