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

Revisions №21218

branch: rosetta:commits 「№21218」
Commited by: lyskov-ai
GitHub Pull Request link: 「№690」
Merge: 「b8e64ecdc」「7f670472f」  code diff
Scheduled at: 2026-05-06 00:08:11.088284
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 №690 RosettaCommons/rosetta/main ← lyskov-ai/rosetta/refactor/bitset-bitvector-rule-of-zero Merge: b8e64ecdc0338b77c231760f7f9bdcd4d500a240←7f670472fa0942db38fbaf9eb58d619b79187a4d Apply Rule of Zero to BitSet and BitVector ---------------- Merge commit message: Apply Rule of Zero to BitSet and BitVector Both class templates have a single value-type member (std::set / std::vector) and no user-declared copy/move/assignment operators, so the explicit empty destructors did nothing the compiler-generated ones wouldn't. They were also suppressing the implicit move constructor and move assignment. Remove the empty `~BitSet() {}` and `~BitVector() {}` declarations so the classes follow the Rule of Zero and gain implicit move support.

...
Test: linux.gcc.mpi.serialization.integration.mpi

Failed sub-tests (click for more details):
replica_docking