Hm. If the constraint doesn't yet exist, the ``setState`` is effectively ignored. I would prefer it threw in such a case as the caller should know the state hasn't been updated, and is most likely to be a developer error (e.g., trying to set an incorrect constraint, or a constraint for a controller that has not yet been constructed).