-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Rips out dead code from the container.hpp and creates for_each_pair.hpp #1882
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
#ifndef FOR_EACH_PAIR_HPP | ||
#define FOR_EACH_PAIR_HPP | ||
|
||
#include <numeric> | ||
#include <iterator> | ||
|
||
namespace osrm | ||
{ | ||
namespace util | ||
{ | ||
|
||
// TODO: check why this is not an option here: | ||
// std::adjacent_find(begin, end, [=](const auto& l, const auto& r){ return function(), false; }); | ||
template <typename ForwardIterator, typename Function> | ||
Function for_each_pair(ForwardIterator begin, ForwardIterator end, Function function) | ||
{ | ||
if (begin == end) | ||
{ | ||
return function; | ||
} | ||
|
||
auto next = begin; | ||
next = std::next(next); | ||
|
||
while (next != end) | ||
{ | ||
function(*begin, *next); | ||
begin = std::next(begin); | ||
next = std::next(next); | ||
} | ||
return function; | ||
} | ||
|
||
template <class ContainerT, typename Function> | ||
Function for_each_pair(ContainerT &container, Function function) | ||
{ | ||
using std::begin; | ||
using std::end; | ||
return for_each_pair(begin(container), end(container), function); | ||
} | ||
|
||
} // namespace util | ||
} // namespace osrm | ||
|
||
#endif /* FOR_EACH_PAIR_HPP */ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
just nit-pitting, but I've read somewhere that it would be best to bring these kind of functions into the namespace (
using std::next
) so that the compiler can decide which next to use, if there should be some better fitting one.Just as you've done below for begin and end.
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 for begin / end I can understand the need for Koenig lookup (so that it e.g. works on raw arrays); next should eventually dispatch to operator++ (for forward iterators), and that the iterator concept guarantees for and lets the user implement it in any way she wishes.