Implements #61
It's still a bit hacky but the compile message should be comprehensive enough that it's obvious whats wrong and removes a unnecessary possibility of panic!, which is especially nice for those of us who work on embedded systems where panic! messages are often unrecoverable.
The only real issue with it is that it breaks the tests for it. I will look into using compiletest_rs to fix this.
jdonszelmann
commented
1 year ago
Implements #61 It's still a bit hacky but the compile message should be comprehensive enough that it's obvious whats wrong and removes a unnecessary possibility of panic!, which is especially nice for those of us who work on embedded systems where panic! messages are often unrecoverable.
The only real issue with it is that it breaks the tests for it. I will look into using compiletest_rs to fix this.