rename func_8002F368, a getter for struct Player -> exchangeItemId
#2358
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 PR invites anyone to discuss and decide on the name
my initial thought was to name it simply
Player_GetExchangeItemId. I've reconsidered to settle forActor_GetPlayerExchangeItemIdnow, though. arguably, the former might be not the best name, as discussed with @fig02 @ #2295 (comment)reasoning
all in all it seems that the general consensus is:
Actor_for common functions%EntityName%_for entity-specific onesso, following this rule,
Actor_GetPlayerExchangeItemIdseems to fit:P.S.
existing functions considered:
Actor_FindNearby: an actor looks up another oneBgDyYoseizo_Vanish: Great Fairy looks up an ocarina spot, besides the main purposeActor_GetProjectileActor: an actor looks up a projectileBgGanonOtyuka_WaitToFall: Ganon looks up a falling platformObjBean_CheckForHorseTrample: Bean plant looks up a horse proximity