We should setup tests in the interface repo to verify all the interfaces it provides. The compliance test repo should have tests to verify if interfaces are supported so the purpose is different.
Agree. The tests from the interfaces can be a subset of the Compliance tests, tho. We can just pull them in CI.
1and so does the
treadyport. The standard explicitly describes some signals as optional and what the default value is. If an interface can't have default values then the user must remember to set these signals explicitly. A user may not even know what the proper default for an unused signal like