The Go FAQ begins the answer to the question, "Is Go an object-oriented language," with, "yes and no."
https://go.dev/doc/faq#Is_Go_an_object-oriented_language The section goes on to say that Go has methods but there is no type hierarchy. I guess those are the yes and no. But I feel like programmers bringing their ideas from other less ambiguously object oriented languages like Java and C++ often have difficulty writing idiomatic Go. If the answer to that question is "yes and no," it'd be less ambiguous to simply say, "no." And that would be a definitive way of indicating that it woul be inappropriate to apply many patterns from object oriented languages to Go -- and to encourage people to accept Go for what it is. Since receivers are parameters and one could use methods without using the method calling syntax at all, I'd suggest we'd classify it as a structured programming language with methods. In either case, is there a way to make the FAQ more clear on this point? -ayan -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAPSh2XBozm9bOe-O3SphET3A3wTif%3D0RiV%3D1Bw6GJkgT3wedLA%40mail.gmail.com.
