It's necessary not to panic in the read function when failing to read an item now, because while AnyLuaValue never fails, other readable types might. (For example, passing {1, "hi", 3} into a Vec<f64> function argument of a Rust callback should raise an error in the lua context, not crash the program.)
It's necessary not to panic in the read function when failing to read an item now, because while
AnyLuaValuenever fails, other readable types might. (For example, passing{1, "hi", 3}into aVec<f64>function argument of a Rust callback should raise an error in the lua context, not crash the program.)