Better error handling about tune HOT 2 CLOSED

Hello @suhr! Thanks for your issue submission!

I am constantly working on improving the error handling concept. Unfortunately, I have no idea how to handle the error you reported as it is a numerical error which can occur at too many locations.

My strategy was to report all regular errors via Result and all numerical errors via .expect("..."). Do you have a good idea how numerical errors should be handled?

from tune.

I am closing this issue with the following outcome:

• Ratio operations no longer panic (to be released with tune-0.25.0). As a result, invalid float values (e.g. negative ones) are accepted by the API and can lead to non-finite (-inf, +inf, NaN) cents values. This is acceptable since all values passed to the API - including finite ones - need to be correct anyway.
• API code using expect in newer modules is expected to be rewritten without panics and with type-level numerical checks soon.
• Panics in executable code are okay.
• Code using unwrap is expected to never crash. If it does nonetheless, this is considered a bug.
• If a panic is observed in the API code, this is considered bug.

from tune.