dps43378 2014-01-31 00:27 采纳率: 0%
浏览 279

从函数返回未导出的类型

Is it considered bad style to return an unexported type from an exported function?
When I've used it, I mostly find it just creates problems.

A better question might be: when is it a good idea to return an unexported type from an exported function.

  • 写回答

2条回答 默认 最新

  • dsg7513 2014-01-31 00:41
    关注

    I would say there's nothing wrong with returning an unexported variable from an exported function. That's what an accessor is by definition.

    That said, I would only do that in the case where there was some logic that needed to occur every time the unexported variable needed to be accessed.

    EDIT: I hope I understand your clarified question.

    If you have an unexported type user struct{} and you return it with NewUser(), would that fit your use case? If so, then that is a factory design pattern and is useful in Go if you do not want a 3rd party developer to directly create a user type object. That way, your "constructor" or "factory" is the only place to get new instances.

    So, is it "bad style"? I'd say it depends on what challenge needs to be overcome.

    评论

报告相同问题?

悬赏问题

  • ¥15 关于#hadoop#的问题
  • ¥15 (标签-Python|关键词-socket)
  • ¥15 keil里为什么main.c定义的函数在it.c调用不了
  • ¥50 切换TabTip键盘的输入法
  • ¥15 可否在不同线程中调用封装数据库操作的类
  • ¥15 微带串馈天线阵列每个阵元宽度计算
  • ¥15 keil的map文件中Image component sizes各项意思
  • ¥20 求个正点原子stm32f407开发版的贪吃蛇游戏
  • ¥15 划分vlan后,链路不通了?
  • ¥20 求各位懂行的人,注册表能不能看到usb使用得具体信息,干了什么,传输了什么数据