Idiomatic Go: using strings or type assertion?

xuanbao · 2018-04-08 03:30:12 · 1138 次点击    
这是一个分享于 2018-04-08 03:30:12 的资源,其中的信息可能已经有所发展或是发生改变。

Consider:

type Maker interface {
    Name() string
    Type() string
}

type BallMaker interface {
    R() int
    Circ() int
}

type SquareMaker interface {
    Width() int
    Perimeter() int
}

If I want to check what my Maker is:

if maker.Type() == ''BallMaker" {
    //make balls
}

Or

s, ok := maker.(SquareMaker)
if ok {
    // make squares
}

Which one is idiomatic?


评论:

rdigel:

I would always choose the type assertion. For one, there's no risk of mistyping the magic string.

whizack:

the short answer is that your question lacks sufficient context. neither are really idiomatic go because a problem like this would not be modeled as multiple interface types that don't satisfy the same interface.

taking a stab at an approximation of your problem, I'd consider doing something like this: https://play.golang.org/p/s9GPE3UId2N

ui7_uy8:

The answer is "it depends", really, especially when the compiler will restrict when you can use the second one.


入群交流(和以上内容无关):加入Go大咖交流群,或添加微信:liuxiaoyan-s 备注:入群;或加QQ群:692541889

1138 次点击  
加入收藏 微博
0 回复
暂无回复
添加一条新回复 (您需要 登录 后才能回复 没有账号 ?)
  • 请尽量让自己的回复能够对别人有帮助
  • 支持 Markdown 格式, **粗体**、~~删除线~~、`单行代码`
  • 支持 @ 本站用户;支持表情(输入 : 提示),见 Emoji cheat sheet
  • 图片支持拖拽、截图粘贴等方式上传