There are some functions I use so often they may b...

# stdlib

[Marc Knaup]

There are some functions I use so often they may be useful for the stdlib 🙂

val <C : CharSequence> C.nonEmpty
	get() = ifEmpty { null }

val <CollectionType : Collection<*>> CollectionType.nonEmpty
	get() = ifEmpty { null }

val <Element> Array<Element>.nonEmpty
	get() = ifEmpty { null }

val actualNonEmptyString = inputString?.nonEmpty ?: error("is required")
val actualNonEmptyList = inputList?.nonEmpty ?: error("is required")

[ilya.gorbunov]

So it replaces string/collection with null if it's empty? Then you can use .ifEmpty { null } instead.

[Marc Knaup]

Thanks, I've updated the definition appropriately.
Given that I use it so often I'd still prefer a single property 😄

[ilya.gorbunov]

The proposed notEmpty extension property name doesn't look as clear as ifEmpty { null}

[Marc Knaup]

nonEmpty is clearer than notEmpty 😁
nullIfEmpty? 🤔
I really don't like the function call just for the null 😅

[aarjav]

+1 for using ifEmpty but a ifNullOrEmpty could be nice. Then again, isNullOrEmpty (and blank for strings) exists. inputString?.takeIf {!it.isNullOrEmpty()} ?: error("required")

[aarjav]

Edited my message for the 7th time or something