-
Notifications
You must be signed in to change notification settings - Fork 3
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
Separate files into modules #36
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.
It's hard to judge if I've checked everything because moving, renaming, refactoring are all combined in one commit. I'll probably catch more things upon re-reviewing.
return self_pointer_like{func(*it)}; | ||
} | ||
|
||
#define CONTAINER_VIEW_ITERATOR_BINARY_PREDICATE(OP) \ |
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.
Might wanna update macro name
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.
There is another such macro in this file I had missed
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.
Yup, I plan to do so in upcoming commits, as this one is only about moving files around and formatting
OP data; \ | ||
return *this; \ | ||
} | ||
#define CLAWS_TAGGED_DATA_PREFIX_OP(OP) \ |
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'm not really convinced moving \
so far to the right helps with readability
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.
Hmm, actually I used clang-format with the configuration file from this repository, but I agree they were moved quite far. I will update the configuration file to align the \
as far left as possible
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.
Oh damn, that clang-format was supposed to be gone (clang format doesn't handle lambdas well, at least back then)
modules/iterator/CMakeSources.cmake
Outdated
|
||
set(MODULE_PUBLIC_HEADERS | ||
"${MODULE_PATH}/circular_iterator.hpp" | ||
"${MODULE_PATH}/iterator_pair.hpp" |
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 think claws::iterator_pair
could be a container actually, but I'm fine with this too
${CMAKE_CURRENT_SOURCE_DIR}/claws/container) | ||
|
||
set(MODULE_PUBLIC_HEADERS | ||
"${MODULE_PATH}/array_ops.hpp" |
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 don't think this belongs here. But it's deprecated anyway, we'll remove this when claws::vect
is in a good state.
/// | ||
/// *Defined in "HandleTypes.hpp"* | ||
/// (TODO: rename to handle_types.hpp)* | ||
/// |
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.
Good idea to get rid of the todo. However the part above is a doc comment, it should stay.
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.
Oh okay, I don't really understand the doc comment then, can you clarify please ?
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 just links the source file, which allows people to easily go and check the implementation
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.
(Doc comments are preceded by ///
or /**
)
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.
Doc was apparently broken (#37 )
Closes #35