30
Things I'm excited for in Go 1.21 (www.sethvargo.com)
submitted 3 years ago by to c/golang@programming.dev
6 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 3 years ago* (last edited 3 years ago) (2 children)

Are you speaking about clear? It’s my understanding that clear doesn’t get you anything. It modifies the object passed to it, sure, but it doesn’t return different types back to the caller.

Edit: I notice this is downvoted- can someone provide feedback if my understanding of clear is incorrect? 🤔

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 years ago (1 child)

    Yeah, talking about clear. And "getting" is meant loosely, in the sense of "the state of the object after calling the function clear". Regardless of whether the object is modified or a copy returned, that's just weird behavior. Why not empty and zero to empty the container or reset objects in the container to their zero values respectively instead?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 years ago

    I see what you're saying. Hmm. I do think that clear will be a nice addition. It does exactly what it says it'll do, "clear" out the object. In that same vein, I think your suggestions would both be solid alternatives.

    It sounds like clear is already on track to become a part of the language, but maybe you could be the first to put in a suggestion for a zero to accompany it in future releases?

  • permalink
  • fedilink
  • source
  • parent