[Go] Updating a few guidelines and clarifying others

[richardpark-msft]

• errors should always be returned by pointer
• NewClient and Client should be favored as the Client name (instead of WidgetClient, for instance)``

[JeffreyRichter]

I'm approving now but please address my comments.

[github-actions]

Hi @richardpark-msft. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[mirusky]

Any plans of full guide for go?

[richardpark-msft]

Any plans of full guide for go?

@mirusky, what kind of guide are you thinking of? This particular document is basically the "here's what Azure SDKs interface must look like" for Go, but not a tutorial/introduction to the language.

We do have some learn.microsoft.com content (and more is always being added):

• Azure for Go developers: https://learn.microsoft.com/en-us/azure/developer/go/
• Take your first steps with Go: https://learn.microsoft.com/en-us/training/paths/go-first-steps/

And each readme should contain links to our examples, for a particular package, on pkg.go.dev (for instance: https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/messaging/azservicebus#pkg-examples)

[RickWinter]

@jhendrixMSFT @JeffreyRichter Any more concerns with this change? Lets get this PR in to increase the value within our guidelines.

[JeffreyRichter]

Some packages may have multiple clients in them and so we can't name them all Client

[mirusky]

Any plans of full guide for go?

@mirusky, what kind of guide are you thinking of? This particular document is basically the "here's what Azure SDKs interface must look like" for Go, but not a tutorial/introduction to the language.

@richardpark-msft I mean, a full guideline for Azure Go SDK, the current guideline lacks many definitions and parts. Giving a ugly DX since it almost doen't have the concrete rules and explanations.

[github-actions]

Hi @richardpark-msft. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[RickWinter]

@richardpark-msft Can you get this across the finish line and checked in.

[github-actions]

Hi @richardpark-msft. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.