Use (float, float) as parameter type for 2D positions #12227
Merged
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.
PR Summary
As noted in #12214, we currently do not have a consistent way of defining the parameter type of 2D positions. Used formats include
tuple
iterable
tuple of 2 floats
(float, float)
tuple of (float, float)
While all are sort of correct, I think it's important to define the length and the element type.
A fully precise definition is
iterable of float of length 2
orlength-2 iterable of float
, which is IMO is not quite readable and scary to less experienced programmers.Therefore, I propose to use
(float, float)
, e.g.This seems simple and clear enough. It concisely defines contained type and size, and does not put emphasis on tuple, which is technically too restrictive as other iterables work as well.