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
As previously discussed in the python lib, unicode decode errors should be explicitly handled by checker authors, see: enowars/enochecker#77
Currently, a decode error would result in Mumble, which is not correct in many situations (for example, if a field stores unprocessed data that can be placed by other teams).
I think this From should therefore go:
The only benefit the Rust implementation has over python is that one must explicitly call ? on the decode - however I am not sure that service authors will correctly use this power.
As previously discussed in the python lib, unicode decode errors should be explicitly handled by checker authors, see:
enowars/enochecker#77
Currently, a decode error would result in Mumble, which is not correct in many situations (for example, if a field stores unprocessed data that can be placed by other teams).
I think this
From
should therefore go:enochecker-rs/src/lib.rs
Line 25 in b02dace
The text was updated successfully, but these errors were encountered: