Resolved FIXME(s) in EntityEvents#2662
Open
a6tumn wants to merge 1 commit into
Open
Conversation
a6tumn
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Addresses two FIXME(s) in EntityEvents. I tried to follow what the comments said as closely as possible, but do let me know if you would like something to be implemented differently. It is possible to avoid the temporary allocation in InfoCommand by having gatherPotentialSpawns(...) return a flag or by always printing the header regardless of the whether the list is populated or not. It's just a command though, so the impact is likely negligible.