is there a reason TypeConstraint is defined in `en...
# development
a
is there a reason TypeConstraint is defined in
engine/addressable.py
instead of
util/objects.py
? phrased differently, would there be an issue if it were to be moved there? the only import used by TypeConstraint or any of its subclasses is
AbstractClass