Aligning type converters with our design goals on error handling

[LVMVRQUXL]

🤔 The problem

Some type converters provided by Kotools Types encapsulate their result in a Result type (the toNotEmptyList function for example).
But this practice increases the complexity of the API by using a concept that is not widely accepted in the Kotlin community. Also, this concept of a possible failure could be easily representable with an absence of value - the null expression.

💡 The idea

For aligning with our design goals on being agnostic about error handling, Kotools Types should provide an explicit API by definition.
This is why we would like to align our type converters with the following principles:

• A type converter without a suffix shouldn't fail.
• A type converter suffixed by OrNull should return null in case of a failure.

✅ Checklist

Here's the checklist to address for implementing this idea:

• New experimental type converters suffixed by OrNull, implemented by:
  • New type converters suffixed by OrNull and OrThrow for StrictlyPositiveDouble #132
  • New type converters suffixed by OrNull and OrThrow for StrictlyPositiveInt #141
  • New type converters suffixed by OrNull and OrThrow for StrictlyNegativeInt #149
  • New type converters suffixed by OrNull and OrThrow for PositiveInt #155
  • New type converters suffixed by OrNull and OrThrow for NegativeInt #171
  • New type converters suffixed by OrNull and OrThrow for NonZeroInt #173
  • New type converters suffixed by OrNull and OrThrow for NotBlankString #174
  • New type converters suffixed by OrNull and OrThrow for NotEmptyList #176
  • New type converters suffixed by OrNull and OrThrow for NotEmptySet #178
  • New type converters suffixed by OrNull and OrThrow for NotEmptyMap #179
• Stabilization of type converters suffixed by OrNull #262
• Deprecation of factory functions using Result #263
• Deprecation promotion of factory functions using Result to error level #265
• Deprecation promotion of factory functions using Result to hidden level #266
• Deletion of factory functions using Result #267
• Deprecation of ResultContext #264
• Deprecation promotion of ResultContext to error level #268
• Deprecation promotion of ResultContext to hidden level #269
• Deletion of ResultContext #270

🙏 Help needed

Please give this post a reaction if you are interested in this change and comment below your thoughts on it.
We would love to have your feedback!

[LVMVRQUXL]

This idea will be documented in an other discussion.

[LVMVRQUXL]

We will implement the idea #315 instead of this one.