fix: correct usage of boost::filesystem::path::extension #148
Conversation
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
caic99
force-pushed
the
boost-fs-ext
branch
2 times, most recently
from
4329e1a to
7eb2c37
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request includes a change to the
simulation_containerstructure in theunidock/src/main/simulation_container.hfile. The change simplifies the code by replacing a call toboost::filesystem::extensionwith a more straightforward method to get the file extension.Code simplification:
unidock/src/main/simulation_container.h: Replacedboost::filesystem::extensionwithpath().extension().string()to determine the file extension ofm_ligand_config_paths[id].path().