You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there are a few functions that use {Option, Result}::expect because there is no way to return Option or Result. Examples are LinearMap::{index, index_mut} , Vec::from_iter and IndexMap::index.
AFIK the messages that are associated with them are statically allocated in the data section of the binary and therefore take up space, even if no panic actualy can occure.
As this library is used with microcontrollers, should those strings be removed?
I don't know if rust is smart enough to remove them from the binary by itself.
However some clarity in panic messages would be sacrificed in exchange for it.
The text was updated successfully, but these errors were encountered:
Currently there are a few functions that use
{Option, Result}::expect
because there is no way to returnOption
orResult
. Examples areLinearMap::{index, index_mut}
,Vec::from_iter
andIndexMap::index
.AFIK the messages that are associated with them are statically allocated in the data section of the binary and therefore take up space, even if no panic actualy can occure.
As this library is used with microcontrollers, should those strings be removed?
I don't know if rust is smart enough to remove them from the binary by itself.
However some clarity in panic messages would be sacrificed in exchange for it.
The text was updated successfully, but these errors were encountered: