-
Notifications
You must be signed in to change notification settings - Fork 225
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.
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
Add AxisAlignedBox::fromPoints
#1114
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @j9liu, just a couple of minor comments here.
@@ -1,9 +1,12 @@ | |||
#pragma once | |||
|
|||
#include <CesiumGeometry/Library.h> | |||
#include "Library.h" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We used to do this for headers in the same directory, but lately we've just been using the qualified name in angle brackets for consistency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay! I thought that went against our style guide, but I'll revert it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be worth adding a section about #include style to the style guide? Especially since this is a change from SF.12.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reopened #991 noting this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can see doing this for #include
s in headers, but a small peeve in .cpp
files is that the angle brackets cause the relevant .h
to get mixed with the other includes. In other words, if I have "MyFile.h"
, doing <MyFile.h>
in MyFile.cpp
potentially mixes it with the other includes due to sorting alphabetically. It's not the biggest deal in the world but I guess the first option feels more "right" :')
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That might be fixable with .clang-format
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm maybe not: llvm/llvm-project#39735
Thanks for the comments @kring ! This is ready for another look. |
Thanks @j9liu! |
This is just a helper function that I plan to use in #1111. That PR is getting a bit heavy, so I wanted to break it up into more digestible PRs.