没有括号，map三元很容易读:

c := map[bool]int{true: 1, false: 0} [5 > 4]

虽然被创作者所回避，但俏皮话也有自己的一席之地。

这个函数解决了惰性求值的问题，它允许你在必要时可选地传递函数来求值:

func FullTernary(e bool, a, b interface{}) interface{} {
    if e {
        if reflect.TypeOf(a).Kind() == reflect.Func {
            return a.(func() interface{})()
        }
        return a
    }
    if reflect.TypeOf(b).Kind() == reflect.Func {
        return b.(func() interface{})()
    }
    return b
}

func demo() {
    a := "hello"
    b := func() interface{} { return a + " world" }
    c := func() interface{} { return func() string { return "bye" } }
    fmt.Println(FullTernary(true, a, b).(string)) // cast shown, but not required
    fmt.Println(FullTernary(false, a, b))
    fmt.Println(FullTernary(true, b, a))
    fmt.Println(FullTernary(false, b, a))
    fmt.Println(FullTernary(true, c, nil).(func() string)())
}

输出

hello
hello world
hello world
hello
bye

传入的函数必须返回一个接口{}以满足内部强制转换操作。 根据上下文，您可以选择将输出强制转换为特定类型。 如果你想从这个函数中返回一个函数，你需要用c来包装它。

这里的独立解决方案也很好，但对于某些用途可能不太清楚。

No Go没有三元运算符。使用if/else语法是惯用的方法。

Why does Go not have the ?: operator? There is no ternary testing operation in Go. You may use the following to achieve the same result: if expr { n = trueVal } else { n = falseVal } The reason ?: is absent from Go is that the language's designers had seen the operation used too often to create impenetrably complex expressions. The if-else form, although longer, is unquestionably clearer. A language needs only one conditional control flow construct. — Frequently Asked Questions (FAQ) - The Go Programming Language

正如所指出的(希望这并不令人意外)，使用if+else确实是在Go中执行条件语句的惯用方式。

除了完整的var+if+else代码块之外，这种拼写也经常被使用:

index := val
if val <= 0 {
    index = -val
}

如果你有一段重复的代码，比如int value = a <= b ?A: b，你可以创建一个函数来保存它:

func min(a, b int) int {
    if a <= b {
        return a
    }
    return b
}

...

value := min(a, b)

编译器将内联这些简单的函数，所以它更快，更清楚，更简短。

没有括号，map三元很容易读:

c := map[bool]int{true: 1, false: 0} [5 > 4]

埃尔德的回答既有趣又有创意，甚至可以说很聪明。

但是，建议改为:

var index int
if val > 0 {
    index = printPositiveAndReturn(val)
} else {
    index = slowlyReturn(-val)  // or slowlyNegate(val)
}

是的，它们都编译成本质上相同的程序集，但是这段代码比调用匿名函数只返回一个可以首先写入变量的值要清晰得多。

基本上，简单清晰的代码比有创意的代码更好。

此外，任何使用map文字的代码都不是一个好主意，因为在Go中映射根本不是轻量级的。自Go 1.3以来，小型地图的随机迭代顺序得到了保证，为了加强这一点，小型地图的内存效率大大降低。

As a result, making and removing numerous small maps is both space-consuming and time-consuming. I had a piece of code that used a small map (two or three keys, are likely, but common use case was only one entry) But the code was dog slow. We're talking at least 3 orders of magnitude slower than the same code rewritten to use a dual slice key[index]=>data[index] map. And likely was more. As some operations that were previously taking a couple of minutes to run, started completing in milliseconds.\