Removes unused variables in G3D:Ray #3040
Merged
Conversation
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
Stoabrogga
pushed a commit
to Stoabrogga/vmangos
that referenced
this pull request
May 27, 2025
(cherry picked from commit 6ac635b)
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.
🍰 Pullrequest
These are unused variables. Idk if the compiler optimizes them out. But if not, thats some heavy branching in ray::set
If we do want to keep them for future use - i don't see why - i have an example that removes some branching by reordering the enum and uses base3: https://github.com/Gamemechanicwow/core/tree/ray-classification-for-collision
Proof
Issues
How2Test
Todo / Checklist