Quoting Victor Giordano (2019-01-16 12:44:57) > "able" describes things in a more "passive way"� (the thing that you > can "ask it/his/her" to do). Do you find this appreciation correct?
Pretty close, but a subtle point is that "-able" makes something the indirect object, so for example it is not quite right to say that a "writable" is something that you can ask to do writing -- it is the thing being written to, whereas the thing doing the writing is a "writer". In the case of io.Writer either one kindof makes sense, but the meaning *is* slightly different. When both are reasonable, -er is generally more idiomatic Go -- but that's not always the case. > The Go idiomatic style is to use the '-er' suffix. But this can > sometimes lead to strange or obscure names even for native English > speakers. > For example, an interface with a "Stale() bool" method seems very > strange when named as "Staler". All these sound weird: Lookuper, > Errorer, Nexter The problem with most of these is that the base words aren't verbs; the -er suffix converts a verb, describing an action, into a noun describing the thing or person that performs that action -- but "next" isn't an action, so "nexter" sounds weird. lookup is a little different -- "I lookup information" scans poorly, and I'd probably write it as "I look up something" or better yet "I look something up" -- so that probably has something to do with it, but I don't know how to describe the rule precisely. Ironically, I often have an easier time describing grammar rules precisely for German, because being a native English speaker I didn't learn English grammar in as structured a way. :P -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. For more options, visit https://groups.google.com/d/optout.
