3 ms·
The problem is with contract versioning. If you're writing a library, and your return types are derived rather than explicit, it's way too easy to break your cl
by int_19h 8y ago
The problem is with contract versioning. If you're writing a library, and your return types are derived rather than explicit, it's way too easy to break your clients by changing the type without even noticing. So maybe require it for public interfaces?
- nickmqb 8y agoI'm not yet convinced to make it absolutely required, but some kind of warning/linter message would definitely be useful for this.