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
{{ message }}
This repository has been archived by the owner on Dec 15, 2021. It is now read-only.
I recently published itm-decode before stumbling upon this crate just now. Comparing the two after a cursory dive, itm seems a bit more general with its application of traits; itm-decode has a more granular error enum, to help with trace streams that diverge from the specification; #34 is being implemented, and an ITM encoder may eventually be implemented for testing purposes with some other tools I'll be implementing as part of my master's. I have yet to compare the test benches. bin/itm-decode.rs shares some features with itmdump.
Perhaps the crates should be merged?
The text was updated successfully, but these errors were encountered:
Another planned feature is the bookkeeping of instrumentation packets. The API is also being refactored to mimic that of this crate (i.e., read data from a Stream<R: std::io::Read>).
tmplt
changed the title
Crate reimplemented. Merge?
Crate reimplemented with more features. Replace?
Nov 21, 2021
I recently published itm-decode before stumbling upon this crate just now. Comparing the two after a cursory dive,
itm
seems a bit more general with its application of traits;itm-decode
has a more granular error enum, to help with trace streams that diverge from the specification; #34 is being implemented, and an ITM encoder may eventually be implemented for testing purposes with some other tools I'll be implementing as part of my master's. I have yet to compare the test benches.bin/itm-decode.rs
shares some features withitmdump
.Perhaps the crates should be merged?
The text was updated successfully, but these errors were encountered: