osrm-backend/include/guidance/turn_lane_augmentation.hpp

#ifndef OSRM_GUIDANCE_TURN_LANE_AUGMENTATION_HPP_
#define OSRM_GUIDANCE_TURN_LANE_AUGMENTATION_HPP_

#include "guidance/intersection.hpp"
#include "guidance/turn_lane_data.hpp"
#include "util/attributes.hpp"

namespace osrm::guidance::lanes
{

OSRM_ATTR_WARN_UNUSED
LaneDataVector handleNoneValueAtSimpleTurn(LaneDataVector lane_data,
                                           const Intersection &intersection);

} // namespace osrm::guidance::lanes

#endif /* OSRM_GUIDANCE_TURN_LANE_AUGMENTATION_HPP_ */
Split intersection analysis and guidance code Intersection analysis occupy in osrm::extractor::intersection namespace and guidance code osrm::guidance 2018-01-05 08:33:53 -05:00			`#ifndef OSRM_GUIDANCE_TURN_LANE_AUGMENTATION_HPP_`
			`#define OSRM_GUIDANCE_TURN_LANE_AUGMENTATION_HPP_`
basic turn lane handling 2016-05-13 13:18:00 -04:00
Move guidance pre-processing code into GUIDANCE library 2018-01-05 07:05:53 -05:00			`#include "guidance/intersection.hpp"`
			`#include "guidance/turn_lane_data.hpp"`
Warn on unused return values in guidance code, resolves #2686. https://github.com/Project-OSRM/osrm-backend/pull/2685/files fixes an issue where we did elongate(fstStep, sndStep); instead of newStep = elongate(fstStep, sndStep); we didn't get any warnings. The only way to trigger a warning here is to use ```cpp __attribute__((warn_unused_result)) ``` This changeset does exactly that: for the new guidance code prone to these kind of issue we add such an attribute to the declaration. 2016-08-02 09:43:29 -04:00			`#include "util/attributes.hpp"`
basic turn lane handling 2016-05-13 13:18:00 -04:00
Use nested namespace It's a mechanical change to modernize the code base 2022-12-11 04:10:26 -05:00			`namespace osrm::guidance::lanes`
basic turn lane handling 2016-05-13 13:18:00 -04:00			`{`

Warn on unused return values in guidance code, resolves #2686. https://github.com/Project-OSRM/osrm-backend/pull/2685/files fixes an issue where we did elongate(fstStep, sndStep); instead of newStep = elongate(fstStep, sndStep); we didn't get any warnings. The only way to trigger a warning here is to use ```cpp __attribute__((warn_unused_result)) ``` This changeset does exactly that: for the new guidance code prone to these kind of issue we add such an attribute to the declaration. 2016-08-02 09:43:29 -04:00			`OSRM_ATTR_WARN_UNUSED`
basic turn lane handling 2016-05-13 13:18:00 -04:00			`LaneDataVector handleNoneValueAtSimpleTurn(LaneDataVector lane_data,`
			`const Intersection &intersection);`

Fix formatting 2022-12-20 12:00:11 -05:00			`} // namespace osrm::guidance::lanes`
basic turn lane handling 2016-05-13 13:18:00 -04:00
Split intersection analysis and guidance code Intersection analysis occupy in osrm::extractor::intersection namespace and guidance code osrm::guidance 2018-01-05 08:33:53 -05:00			`#endif /* OSRM_GUIDANCE_TURN_LANE_AUGMENTATION_HPP_ */`