Skip to content

Fix formatting #1489

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 23, 2025
Merged

Fix formatting #1489

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/bsoncxx/lib/bsoncxx/v1/exception.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,8 @@ namespace v1 {
// - https://lld.llvm.org/missingkeyfunction:
// > It’s always advisable to ensure there is at least one eligible function that can serve as the key function.
// - https://gcc.gnu.org/onlinedocs/gcc/Vague-Linkage.html
// > For polymorphic classes (classes with virtual functions), the ‘type_info’ object is written out along with the vtable.
// > For polymorphic classes (classes with virtual functions), the ‘type_info’ object is written out along with the
// vtable.
void exception::key_function() const {}

} // namespace v1
Expand Down
3 changes: 2 additions & 1 deletion src/mongocxx/lib/mongocxx/v1/exception.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,8 @@ std::error_category const& type_error_category() {
// - https://lld.llvm.org/missingkeyfunction:
// > It’s always advisable to ensure there is at least one eligible function that can serve as the key function.
// - https://gcc.gnu.org/onlinedocs/gcc/Vague-Linkage.html
// > For polymorphic classes (classes with virtual functions), the ‘type_info’ object is written out along with the vtable.
// > For polymorphic classes (classes with virtual functions), the ‘type_info’ object is written out along with the
// vtable.
void exception::key_function() const {}

} // namespace v1
Expand Down