Mixed pointer and value recivers about uuid HOT 4 CLOSED

https://go.dev/tour is a beginners tutorial to the language. Does it cause any demonstrable issues?

from uuid.

Does it cause any demonstrable issues?

I'll second this point. Much of the code in this repo came from github.com/satori/go.uuid so we (the current maintainers) aren't fully responsible for the decisions that were made there. I'd argue against making a purely cosmetic change for this.

FWIW, I'd support following this "rule" for any new code.

from uuid.

Does it cause any demonstrable issues?

Pointer receiver means that instance can be nil instead of value receiver which cause segfault in that situation.

from uuid.

FWIW, I'd support following this "rule" for any new code.

There are much better UUID library.

from uuid.