-
Notifications
You must be signed in to change notification settings - Fork 82
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
[INFRA] Move core/algorithm into core/configuration #2255
[INFRA] Move core/algorithm into core/configuration #2255
Conversation
a0f7a83
to
0befa64
Compare
include/seqan3/core/configuration/detail/configuration_utility.hpp
Outdated
Show resolved
Hide resolved
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.
Thank you!
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.
Please do not remove the old seqan3/alignment/band in this PR. This has nothing to do with the change of the configuration header. Second the static band should be deprecated before it is removed in 3.1. Can you first revert these changes and then I look into the rest. Thank you
64f920c
to
52e071c
Compare
#include <seqan3/core/algorithm/configuration_utility.hpp> | ||
#include <seqan3/core/algorithm/configuration.hpp> | ||
#include <seqan3/core/detail/pack_algorithm.hpp> | ||
#include <seqan3/core/algorithm/detail/all.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.
please remove
#include <seqan3/core/algorithm/pipeable_config_element.hpp> | ||
#include <seqan3/core/configuration/all.hpp> // ToDo: remove this with the release SeqAn-3.1.0. |
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.
Not sure how to handle this. This is likely to be forgotten.
I am thinking of this:
#if SEQAN3_VERSION_MAJOR == 3 && SEQAN3_VERSION_MINOR == 1
#pragma warning "Remove #include <seqan3/core/configuration/all.hpp> from this header."
#endif
@marehr what do you think?
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.
This was exactly the problem I tried to explain on Gitter on friday..
* \author Rene Rahn <rene.rahn AT fu-berlin.de> | ||
* \deprecated This header will be removed in 3.1. Please use seqan3/core/configuration/detail/concept.hpp instead. |
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.
* \deprecated This header will be removed in 3.1. Please use seqan3/core/configuration/detail/concept.hpp instead. | |
* \deprecated This header will be removed in 3.1.0; Please \#include <seqan3/core/configuration/detail/concept.hpp> instead. |
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 followed Marcel's example, which he created for us. (math) Now I had to make a lot of changes that did not match his example. Maybe next time you can look over the example as the core team before we take over all the mistakes there.
* \deprecated This header will be removed in 3.1. Please use | ||
* seqan3/core/configuration/detail/configuration_element_debug_mode.hpp instead. |
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.
* \deprecated This header will be removed in 3.1. Please use | |
* seqan3/core/configuration/detail/configuration_element_debug_mode.hpp instead. | |
* \deprecated This header will be removed in 3.1.0; Please \#include <seqan3/core/configuration/detail/configuration_element_debug_mode.hpp> instead. |
"This header is deprecated and will be removed in SeqAn-3.1.0; Please #include " | ||
"<seqan3/core/configuration/detail/configuration_element_debug_mode.hpp> instead.") |
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.
"This header is deprecated and will be removed in SeqAn-3.1.0; Please #include " | |
"<seqan3/core/configuration/detail/configuration_element_debug_mode.hpp> instead.") | |
"This header is deprecated and will be removed in SeqAn-3.1.0; Please #include <seqan3/core/configuration/detail/configuration_element_debug_mode.hpp> instead.") |
We said that it is ok to not wrap this around. I think it causes some displaying issues.
* \deprecated This header will be removed in 3.1. Please use | ||
* seqan3/core/configuration/detail/configuration_element_parallel_mode.hpp instead. |
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.
* \deprecated This header will be removed in 3.1. Please use | |
* seqan3/core/configuration/detail/configuration_element_parallel_mode.hpp instead. | |
* \deprecated This header will be removed in 3.1.0; Please \#include | |
* <seqan3/core/configuration/detail/configuration_element_parallel_mode.hpp> instead. |
"This header is deprecated and will be removed in SeqAn-3.1.0; Please #include " | ||
"<seqan3/core/configuration/detail/configuration_element_parallel_mode.hpp> instead.") |
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.
"This header is deprecated and will be removed in SeqAn-3.1.0; Please #include " | |
"<seqan3/core/configuration/detail/configuration_element_parallel_mode.hpp> instead.") | |
"This header is deprecated and will be removed in SeqAn-3.1.0; Please #include <seqan3/core/configuration/detail/configuration_element_parallel_mode.hpp> instead.") |
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.
Is your requested change here, that you want everything in one line, even if there are more than 120 characters?
* \deprecated This header will be removed in 3.1. Please use seqan3/core/configuration/detail/configuration_utility.hpp | ||
* instead. |
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.
* \deprecated This header will be removed in 3.1. Please use seqan3/core/configuration/detail/configuration_utility.hpp | |
* instead. | |
* \deprecated This header will be removed in 3.1.0; Please \#include <seqan3/core/configuration/detail/configuration_utility.hpp> | |
* instead. |
"This header is deprecated and will be removed in SeqAn-3.1.0; Please #include " | ||
"<seqan3/core/configuration/detail/configuration_utility.hpp> instead.") |
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.
"This header is deprecated and will be removed in SeqAn-3.1.0; Please #include " | |
"<seqan3/core/configuration/detail/configuration_utility.hpp> instead.") | |
"This header is deprecated and will be removed in SeqAn-3.1.0; Please #include <seqan3/core/configuration/detail/configuration_utility.hpp> instead.") |
@@ -13,4 +13,5 @@ | |||
#pragma once | |||
|
|||
#include <seqan3/core/algorithm/detail/algorithm_executor_blocking.hpp> | |||
#include <seqan3/core/algorithm/detail/execution_handler_parallel.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 in general we don't want detail to be included inside of the all.hpp.
It basically is no functionality for the user and should be included through the public headers.
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.
So we leave it for now but I would remove it later. Lets discuss this today in the group meeting
You might want to check my changes before I rebase. |
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.
OK one small thing. I couldn't find the header that should be removed later? The warning is only a message emitted by the compiler. The header include should still exist. Or did I miss it? You can rebase right away.
#include <seqan3/core/algorithm/pipeable_config_element.hpp> | ||
#if SEQAN3_VERSION_MAJOR == 3 && SEQAN3_VERSION_MINOR == 1 | ||
#pragma warning "Remove #include <seqan3/core/configuration/all.hpp> from this header." |
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.
but where is the header?
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.
working without the head... 😅
8e11176
to
8f7ac72
Compare
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.
some minor include order then it is good to go
#include <seqan3/core/configuration/detail/concept.hpp> | ||
#include <seqan3/core/concept/tuple.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.
include order
algorithm/concept.hpp -> core/configuration/detail/. algorithm/configuration.hpp -> core/configuration/. algorithm/configuration_element_debug_mode.hpp -> core/configuration/detail/. algorithm/configuration_element_parallel_mode.hpp -> core/configuration/detail/. algorithm/configuration_utility.hpp -> core/configuration/detail/. Skipped: algorithm/pipeable_config_element.hpp (needs a decision) Keep untouched: algorithm/detail/... -> core/algorithm/detail/... algorithm/algorithm_result_generator_range -> core/algorithm/algorithm_result_generator_range Added new all.hpp's and adjusted the other ones. Signed-off-by: Lydia Buntrock <[email protected]>
8f7ac72
to
1ae6a3f
Compare
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.
Thank you
PR seqan#2255 did the move from core/algorithm into core/configuration, but at the same time PR seqan#2247 changed one header. This seems like a misinterpreted merge conflict and this PR reintroduces the changes from seqan#2255. After checking the changes of seqan#2255, this seems to be the only missed change. This partially reverts commit 1ae6a3f.
PR seqan#2255 did the move from core/algorithm into core/configuration, but at the same time PR seqan#2247 changed one header. This seems like a misinterpreted merge conflict and this PR reintroduces the changes from seqan#2255. After checking the changes of seqan#2255, this seems to be the only missed change. This partially reverts commit 1ae6a3f.
Resolves partly seqan/product_backlog#160
algorithm/concept.hpp -> core/configuration/detail/.
algorithm/configuration.hpp -> core/configuration/.
algorithm/configuration_element_debug_mode.hpp -> core/configuration/detail/.
algorithm/configuration_element_parallel_mode.hpp -> core/configuration/detail/.
algorithm/configuration_utility.hpp -> core/configuration/detail/.
Skipped: algorithm/pipeable_config_element.hpp (needs a decision)
Keep untouched:
algorithm/detail/... -> core/algorithm/detail/...
algorithm/algorithm_result_generator_range -> core/algorithm/algorithm_result_generator_range
Added new all.hpp's and adjusted the other ones.
Details for this: https://gist.github.com/rrahn/f6b09ad67bebd14bd9c58f77c53e0450