douxu3315 2019-07-20 13:37
浏览 94
已采纳

golang是否会复制整个接收者的值?

I am almost sure of that but I want to be 100% sure. Because this seems weird after JS/PHP.

type Vertex struct {
    X, Y float64
}

func (v Vertex) Scale(f float64) {
    v.X = v.X * f
    v.Y = v.Y * f
}

So is it true that a deep copy (emphasize on this) of v Vertex parameter will be made on every Scale invocation? And therefore, we should use pointer receivers instead of value receivers in order to avoid the deep-copying?

And the same applies to parameters, right? What are other places where the copying happens?

  • 写回答

2条回答 默认 最新

  • douxue4242 2019-07-20 13:38
    关注

    Yes, a copy is made. Use pointer receivers if the value is large, you care about avoiding copies, and there are no other considerations (like wanting a copy for various reasons).

    The Go FAQ has a useful entry on value vs. pointer receivers.

    Note that a copy is made, but you say "deep copy" so be careful here - usually deep copy implies recursive copies including what pointers point to (like copying a whole tree). The copy here is a shallow copy. If Vertex has pointer fields, the values of these pointers will be copied, but not what they point to. There is plenty of discussion of shallow vs. deep copies in Go online; for example this SO question. If there are struct fields, the values of these will also be copied, so it's "deep" in the sense of struct nesting, but not "deep" in the sense of pointers.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论
查看更多回答(1条)

报告相同问题?

悬赏问题

  • ¥15 matlab答疑 关于海上风电的爬坡事件检测
  • ¥88 python部署量化回测异常问题
  • ¥30 酬劳2w元求合作写文章
  • ¥15 在现有系统基础上增加功能
  • ¥15 远程桌面文档内容复制粘贴,格式会变化
  • ¥15 关于#java#的问题:找一份能快速看完mooc视频的代码
  • ¥15 这种微信登录授权 谁可以做啊
  • ¥15 请问我该如何添加自己的数据去运行蚁群算法代码
  • ¥20 用HslCommunication 连接欧姆龙 plc有时会连接失败。报异常为“未知错误”
  • ¥15 网络设备配置与管理这个该怎么弄