Closed dlfivefifty closed 5 years ago
Ah, I see, they are used because the domains are mapped domains.
Though I think my point is still correct: 2*UnitBall()
is arguably clearer than ball(2)
.
In the absence of a type that stores a centre and radius, it seemed user-friendly to provide a routine that would return a domain that represents what the user wants. They are lower-cased because you can't predict which type they return. Right now they are indeed mapped domains. How about ball(radius=2)
?
But I agree there shouldn't be too many of these.
I think 2UnitBall()
is pretty user friendly
I can live with that
Some will need to stay for now: e.g. ellipse
There are too many convenience functions, which goes against a good practice code design principle that there should only be one way to write anything (to make find-and-replace easier, etc.). I think all the lowercase convenience functions can be removed:
UnitDisk
is just as good asdisk
, etc.