Guarded accessing phyloref.internalSpecifiers/externalSpecifiers #133
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
gaurav
force-pushed
the
remove-unguarded-external-specifiers
branch
from
91727fd to
4527b9d
Compare
gaurav
changed the title
hlapp
approved these changes
Jul 19, 2023
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.
While working on Klados, I discovered that some uses of
phyloref.internalSpecifiers/phyloref.externalSpecifiersare not guarded: we access those variables without checking to see if they exist. Generally this causes an error that is simply ignored. But since it is an easy fix, I went ahead and fixed them in this PR.Should be merged after PR #127.