My own preference is to have a small number of methods and put the general functionalities into functions. By putting the general functionalities into functions, you allow code reuse. In object-oriented programming, you normally attach as many functionalities as possible to their corresponding types and achieve code reuse via inheritance. Since Go does not have inheritance, you can achieve a similar effect with standalone functions.
On Friday, March 18, 2022 at 11:26:51 AM UTC+7 Ian Lance Taylor wrote: > On Thu, Mar 17, 2022 at 7:17 PM Zhaoxun Yan <yan.z...@gmail.com> wrote: > > > > I just came across this taboo in golang - new methods cannot be added to > an existing type: > > Yes. If we didn't have this prohibition, then the set of interfaces > satisfied by a type would depend on which package was using the type. > > See the discussion at https://go.dev/issue/21401. > > Ian > -- 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/85108bf6-e283-4def-a940-8318f833968cn%40googlegroups.com.