dt2015 2019-04-10 02:20
浏览 46
已采纳

在闭包上使用方法更好吗?

I have a simple type of data that only consists of an uint32, but many operations can be performed on this data. All files that use this data reside in the same package and therefore can access the unexported uint32 inside the struct which is not preferable. I recently learned about the power of closures and was wondering if it is better to use a struct that contains functions that perform the tasks or to have the uint32 stored in the struct and then just use methods with a receiver of the struct.

This is a basic representation of an OpenGL shader. Both the method and closure options, look the same to the caller but perform differently under the hood.

Closure:

type Shader struct {
    getID  func() uint32
    delete func()
}

func CreateShader(shader string) Shader {
    var id uint32
    //Do work...
    return Shader{
        getID: func() uint32 {
            return id
        },
        delete: func() {
            gl.DeleteShader(id)
        },
    }
}

Methods:

type Shader struct {
    id uint32
}

func CreateShader(shader string) Shader{
    var id uint32
    //Do work...
    return Shader{id: id}
}

func (s Shader) getID() uint32 {
    return s.id
}

func (s Shader) delete() {
    gl.DeleteShader(s.id)
}

Both options appear like this in use:

func main() {
    shader := CreateShader("shader.code")
    id := shader.getID()
    fmt.Println(id)
    shader.delete()
}

The miss use I thought to avoid was that the caller could affect the id type without Shader knowing. Something similar to:

shader.id = 4102 // or some other change

With the use of closures this behavior is impossible and requires the caller to go use the proper calls.

As mentioned in the comments, it is possible to use a shader package and unexport the shader type. I didn't use this because I thought it was improper to make an entire package just to hold one file. But perhaps it is proper if it solidifies correct use of the type.

Is there any reason that the closure version is "wrong" compared to the methods? Are there any golang standards that would classify either choice better suited for my use case? I expect the caller to not touch the id of the shader and think that the use of closures makes it clearer the proper use of the shader type.

  • 写回答

1条回答 默认 最新

  • dongyao8698 2019-04-10 06:19
    关注

    Closures and methods solve entirely different problems, so it's rare that you should ever ask which one to use in a particular situation.

    Having said that, closures can be a way to provide data protection, and are often (ab)used for this in languages which don't otherwise offer private variables (i.e. JavaScript).

    There's no reason to ever use them for this purpose in Go.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论

报告相同问题?

悬赏问题

  • ¥15 Chrome Manifest扩展引用Ajax-hook库拦截请求失败
  • ¥15 用Ros中的Topic通讯方式控制小乌龟的速度,走矩形;编写订阅器代码
  • ¥15 LLM accuracy检测
  • ¥15 pycharm添加远程解释器报错
  • ¥15 如何让子窗口鼠标滚动独立,不要传递消息给主窗口
  • ¥15 如何能达到用ping0.cc检测成这样?如图
  • ¥15 关于#DMA固件#的问题,请各位专家解答!
  • ¥15 请问华为OD岗位的内部职业发展通道都有哪些,以及各个级别晋升的要求
  • ¥20 微信小程序 canvas 问题
  • ¥15 系统 24h2 专业工作站版,浏览文件夹的图库,视频,图片之类的怎样删除?