I think I was also suggesting this previously. Should also do the same-named template helper.

If you google "Iif", it also matches a lot, and also easy to remember (inline-if)

TBH I don't like Ternary personally.

It's your call - this isn't a high effort PR and it's usefulness subjective.

My primary issues with Iif vs Ternary is the first one is marked by spellchecking as not a word and looks like I pressed i twice on accident.
TBH I had no idea Iif isn't just a made up term but it's used somewhere else, so TIL. Thanks :)

Share the background about the naming decision:

• We need some handy util functions to make Golang could take a true/false value easily.
• Ternary means "an operator for three operands", not only for the "if" checking. It is a too general name.
• There is a "if" family like util.IfZero
• Gitea heavily uses SQL and IIF is a widely used SQL function name, and it also exists in some other languages. So it won't be too surprising for most developers.
• Then candidate names:
  • iif: it doesn't work because Golang forces public functions should have a upper-case first-letter.
  • IIF: all upper-case doesn't read like "Golang" style
  • InlineIf: it seems wordy
  • If: it is not a real "if" and it evaluate the values before checking the expression.

Wiki: https://en.wikipedia.org/wiki/Ternary_conditional_operator (the real name is ternary conditional operator)

Okay, fair enough, I see the logic.