aboutsummaryrefslogtreecommitdiff
path: root/tests/logs/eod-specs/Vindicator-20220307.zevtc
diff options
context:
space:
mode:
authorDaniel Schadt <kingdread@gmx.de>2021-11-13 12:09:02 +0100
committerDaniel Schadt <kingdread@gmx.de>2021-11-13 12:09:02 +0100
commitd98c391571ac41af08757c3fb87beef0a6415d23 (patch)
treeb3744e7de930f3fd13e82a80720ff84002c3c4ee /tests/logs/eod-specs/Vindicator-20220307.zevtc
parent0aee5f34c9f384656740666c6fdc03ccf537d2a3 (diff)
downloadevtclib-d98c391571ac41af08757c3fb87beef0a6415d23.tar.gz
evtclib-d98c391571ac41af08757c3fb87beef0a6415d23.tar.bz2
evtclib-d98c391571ac41af08757c3fb87beef0a6415d23.zip
Document panic in Log::boss and remove other panic
Overall, evtclib is doing quite well on the .unwrap()/.expect()/panic!() calls, except for some doctests (which can be changed at some point) and the actual tests. One case where we do panic (and should document it!) is Log::boss. The documentation has been added there. Another (rare if not impossible for proper evtc files) case was the conversion of the language event, which assumed that we will definitely be able to convert the u64 to the right language. In all normal cases this should be true, but if evtclib deals with untrusted input, we might not want to panic a whole program because someone smuggled in a malicious file.
Diffstat (limited to 'tests/logs/eod-specs/Vindicator-20220307.zevtc')
0 files changed, 0 insertions, 0 deletions