digactualhole() bit
I'm pretty sure this check at_u should be included since x,y can be passed to digactualhole(). The lack of any related bug reports suggest that at_u is currently always true for any code that calls digactualhole().
This commit is contained in:
Reference in New Issue
Block a user