Maybe this sort of thing doesn’t happen too often, but it’s something I’ve started noticing more and more as I read code in the wild.ĭid I miss a case where takeIf() and takeUnless() would be appropriate, or a case when they introduce errors? Let me know, I’m always happy to chat and appreciate feedback. With over 42 million users in 2020, Duolingo is a well-known language learning platform. On the other hand, it feels like calling takeIf() or takeUnless() on an expression should at least be a warning in IntelliJ. The takeIf() and takeUnless() functions aren’t doing anything you can’t do with if/else, it just makes things easier to read in some cases (which I value highly when writing code). I like the fact if is an expression in Kotlin, and I think that reduces some of the utility of takeIf() and takeUnless(). I do find places in my code to use it, but more often than not I use an if/else expression instead. Represents a range of values (for example, numbers or characters) where both the lower and upper bounds are included in the range. Infrastructure for China (AliCloud or openshift or any other option) to deploy the DSM APIs.

DSM APIs rolled out to all markets (except for China) and all consumers shifted to new APIs. Closing ThoughtsĪs we’ve seen, the places where we might use takeIf() and takeUnless() can be fairly subjective. Capability uplifts that can enable direct connections to new DMPs without Centiro, for example - Data persistence, and non-functional testing. takeIf Īgain, it’s subjective that the takeIf() version is any better, but some might find easier to read. Kotlin is a powerful language that reduces a lot of boilerplate code required to perform basic operations in comparison to Java.

Any kotlin example