---
title: "Comment by Aaron Cohen on \"When Should You Use Pointers in Go\" | Hashnode"
description: "Another reason to use pointers is if one method of the API uses a pointer. Best practice is then to have all methods take pointers even if not necessary. That d"
url: "https://hashnode.com/posts/when-should-you-use-pointers-in-go/618d2f3ff991b025366e2c8c/comment/6425b1a2975e3bb9a50f55bd"
---

[Discussion](https://hashnode.com/posts/when-should-you-use-pointers-in-go/618d2f3ff991b025366e2c8c)

Comment [When Should You Use Pointers in Go](https://hashnode.com/posts/when-should-you-use-pointers-in-go/618d2f3ff991b025366e2c8c)

[Aaron Cohen](https://hashnode.com/@cohenaa)

[Mar 30, 2023](https://hashnode.com/posts/when-should-you-use-pointers-in-go/618d2f3ff991b025366e2c8c/comment/6425b1a2975e3bb9a50f55bd)

Another reason to use pointers is if one method of the API uses a pointer. Best practice is then to have all methods take pointers even if not necessary. That decreases cognitive load on your API consumers.
