> After discussion with Konrad, I'll leave the markdown as is since I
> consistently use code blocks.
>
> After discussion with Roberto, I'll leave the name of "Wifiaper" interface as
> is for consistency with golang interface naming conventions.
A note here about the name of the interface:
https://golang.org/doc/effective_go.html#interface-names says "one-method interfaces are named by the method name plus an -er suffix or similar modification to construct an agent noun". But nothing specific says about interfaces having more than one method. So, golang naming conventions nothing say about this case. (or at least I haven't found anything)
> After discussion with Konrad, I'll leave the markdown as is since I
> consistently use code blocks.
>
> After discussion with Roberto, I'll leave the name of "Wifiaper" interface as
> is for consistency with golang interface naming conventions.
A note here about the name of the interface:
https:/ /golang. org/doc/ effective_ go.html# interface- names says "one-method interfaces are named by the method name plus an -er suffix or similar modification to construct an agent noun". But nothing specific says about interfaces having more than one method. So, golang naming conventions nothing say about this case. (or at least I haven't found anything)