-
Notifications
You must be signed in to change notification settings - Fork 923
Core: Better scaling explicit indirect conditions #4582
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
Open
Mysteryem
wants to merge
2
commits into
ArchipelagoMW:main
Choose a base branch
from
Mysteryem:better_explicit_indirect_condition_scaling
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+5
−3
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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 hidden or 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
Oops, something went wrong.
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.
is this faster? my understanding is dict.get() essentially does this same thing so this just skips the
is not None
checkThere 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.
No, catching exceptions is slow. Exceptions are not meant to be a default codepath, they are for handling exceptional circumstances.
If the expectation was that almost all regions would be present in
self.multiworld.indirect_connections
, and that a region not being present was an 'exceptional circumstance', then the try-except could be faster. It really just depends on what percentage of the time you are expecting to have to catch an exception.My understanding of
dict.get()
is that it is pretty close tomy_dict[key] if key in my_dict else None
, but slightly faster for types with more complex, non-cached hashing becausedict.get()
should only need to get the hash ofkey
once when the key is present in the dictionary, whereasmy_dict[key] if key in my_dict else None
has to hashkey
twice when the key is present.