4 ms·
>Unless every possible error scenario gets its own descriptive error I mean that's not out of the question, I force that in every codebase I use. The only one
by RetpolineDrama 3y ago
>Unless every possible error scenario gets its own descriptive error
I mean that's not out of the question, I force that in every codebase I use. The only one I find that difficult in is Kotlin, because it's a trash language that doesn't properly compose throwables.
- Clamchop 3y agoI'm always amused to read such strong opinions but I also don't know what you're talking about that would be Kotlin's fault.
- jeroenhd 3y agoI don't get it, you can compose exceptions in Kotlin just fine. I believe Jetbrains Compose adds some restrictions on try/catch but even then there are different ways you can communicate failure.
- wiseowise 3y ago> because it's a trash language that doesn't properly compose throwables. Can you elaborate?