Re:Baby Steps: Slowly Porting Musl to Rust
by nwmcsween on Monday June 13, 2016 @09:02PM
(#11899055)
Because the caller shouldn't know specifics on what is valid for the callee unless the caller has a specific and different value of valid. You don't leak information from separate functions this is how you get brittle garbage code.
Re:Baby Steps: Slowly Porting Musl to Rust
by programmer_dude on Wednesday June 15, 2016 @08:11AM
(#11908775)
> caller shouldn't know specifics on what is valid for the callee
Why? How do you even use an API if you don't know what you can pass into it?
Re:Baby Steps: Slowly Porting Musl to Rust
by nwmcsween on Wednesday June 15, 2016 @01:21PM
(#11910638)
For example strtol, you may pass whatever (implicitly nul terminated, which is bad) and it either returns a value or an error. I wasnt advocating _you_ don't know what to pass but that the caller doesn't include specifics of the callee.
Especially for embedded systems, I want the system to blow up on the developer's desk, not in the field, so I'd prefer to fail early.