refactor(profiling): ErrnoBackup::new is safe#3659
Conversation
|
✨ Fix all issues with BitsAI or with Cursor
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3659 +/- ##
==========================================
- Coverage 62.21% 62.20% -0.02%
==========================================
Files 141 141
Lines 13387 13387
Branches 1753 1753
==========================================
- Hits 8329 8327 -2
- Misses 4260 4263 +3
+ Partials 798 797 -1 see 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Benchmarks [ profiler ]Benchmark execution time: 2026-02-17 22:27:09 Comparing candidate commit 214d830 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 29 metrics, 7 unstable metrics. |
Description
In code review, I noticed
ErrnoBackup::newwas safe, but it was already merged. So I fixed it, and added safety comments. We also verify that it is !Send, because it's not safe to write to another thread's errno, which would happen if we sentErrnoBackupto another thread.Reviewer checklist