「view this page in B3 βῆτα server」

Revisions №21187

branch: rosetta:commits 「№21187」
Commited by: lyskov-ai
GitHub Pull Request link: 「№665」
Merge: 「f9c5b025a」「776a3e20b」  code diff
Scheduled at: 2026-04-30 10:26:08.526451
linux.clang linux.gcc linux.srlz mac.clang
debug
release
unit
mac.clang.python38.PyRosetta.unit ubuntu.clang.cxx11thread.serialization.python38.PyRosetta.unit mpi mpi.serialization build.header build.levels build.ninja_debug beautification code_quality.cppcheck code_quality.merge_size serialization code_quality.submodule_regression integration.mpi integration.release_debug integration.tensorflow integration.thread integration.torch integration performance profile linux.clang.score linux.gcc.score mac.clang.score scripts.pyrosetta scripts.rosetta.parse scripts.rosetta.validate scripts.rosetta.verify util.apps windows.build.debug windows.build.release

Pull Request №665 RosettaCommons/rosetta/main ← lyskov-ai/rosetta/refactor/timer-delete-copy Merge: f9c5b025aa6240de1105fd6cdcf04f7a535ea67d←776a3e20b99c27214dd542508fbf49c8056c617f Explicitly delete copy constructor and assignment in Timer ---------------- Merge commit message: Explicitly delete copy constructor and assignment in Timer Timer's destructor calls Report(), printing the elapsed time. Without explicit copy deletion, a copied Timer would silently produce a second Report() call on destruction, logging a duplicate timing entry for the same measured interval. Both tag_ and t_ are non-owning pointers so there is no memory-safety risk, but the semantic hazard is real. Deleting copy constructor and copy assignment makes the non-copyable intent explicit.

Rosetta Benchmark 1 week
Tests for this revision was automatically canceled because newer set of tests for pull-request №665 was submitted!
...