I agree a well used ternary can be more readable than the alternatives. I’ve alternated between
let array = item != nil ? [item!] : []
and
let array = item.map { [$0] } ?? []
I’m not all that satisfied with either alternative. To me the map option is better than spreading the assignment over six lines, but it still creates more cognitive load than seems necessary. The force unwrap is probably more readable (but of course that still leaves a force unwrap), and works where map won’t here:
let optionalD = optionalA != nil ? optionalA!.optionalB : optionalC
However, I don’t think an implicit unwrap here is appropriate without going full Kotlin auto unwrap.
I wouldn’t mind seeing an expanded ternary to cover optionals and enums, perhaps with a keyword patterned after case let. For example:
let array = when let _item = item ? [_item] : []
or
enum E { case a(Int), b(Int) }
let array = when case let .a(_item) = e ? [_item] : []