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. |
||
|---|---|---|
| .. | ||
| contractor | ||
| engine | ||
| extractor | ||
| osrm | ||
| server | ||
| storage | ||
| util | ||