Skip to content

feat(tick): custom debug implementations#275

Open
martintmk wants to merge 1 commit intomainfrom
tick/debug
Open

feat(tick): custom debug implementations#275
martintmk wants to merge 1 commit intomainfrom
tick/debug

Conversation

@martintmk
Copy link
Member

the default debug implementation was too noisy

@codecov
Copy link

codecov bot commented Feb 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (f9dfbba) to head (9869768).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #275   +/-   ##
=======================================
  Coverage   100.0%   100.0%           
=======================================
  Files         140      140           
  Lines        8620     8636   +16     
=======================================
+ Hits         8620     8636   +16     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.


impl std::fmt::Debug for ClockControl {
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
let state = self.state.lock().expect("acquiring lock must always succeed");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just unwrap() in more verbose form. Is there a reason we expect acquiring the lock to always succeed? If so, we should document that reason in the expect-message (i.e. what makes it impossible for this lock to get poisoned).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments