I wonder if these kinds of asserts would give better compile errors than just something like 
```
the method `with_disabled_hfxo` exists for struct `Clocks<Disabled, HfXo<40000000>, Disabled, Disabled, ..., ..., ...>`, but its trait bounds were not satisfied
the full type name has been written to '/home/bogdan/Workspace/Projects/RustPlay/target/debug/deps/RustPlay-e43e58f494c2b30b.long-type-14343517032053736090.txt'
consider using `--verbose` to print the full type name to the consolerustcClick for full compiler diagnostic
main.rs(16, 18):
cmu.rs(402, 1): doesn't satisfy `HfXo<40000000>: IsNotHfXo`
cmu.rs(16, 1): method `with_disabled_hfxo` not found for this struct
cmu.rs(299, 15): trait bound `HfXo<40000000>: IsNotHfXo` was not satisfied
cmu.rs(387, 1): the trait `IsNotHfXo` must be implemented
the method `with_disabled_hfxo` exists for struct `Clocks<Disabled, HfXo<40000000>, Disabled, Disabled, ..., ..., ...>`, but its trait bounds were not satisfied
the full type name has been written to '/home/bogdan/Workspace/Projects/RustPlay/target/debug/deps/RustPlay-310d21680622ddd8.long-type-15144868983527332610.txt'
consider using `--verbose` to print the full type name to the consolerustcClick for full compiler diagnostic
main.rs(16, 18):
cmu.rs(402, 1): doesn't satisfy `HfXo<40000000>: IsNotHfXo`
cmu.rs(16, 1): method `with_disabled_hfxo` not found for this struct
cmu.rs(299, 15): trait bound `HfXo<40000000>: IsNotHfXo` was not satisfied
cmu.rs(387, 1): the trait `IsNotHfXo` must be implemented
```