On Mon, Dec 24, 2018 at 10:24 AM Mark Volkmann <r.mark.volkm...@gmail.com> wrote: > > I guess my question boils down to what should be displayed in the index > section under a type. Currently it seems the answer is ... > If the type is a struct or interface, list all the package functions that > return that type. > If the type is a struct, list all its methods. > If the type is a struct, do not list its fields. > If the type is an interface, do not list its methods. > > I wonder if those two "do not" lines are really desirable. > > The other issue is that you can't tell from the index section whether > something is a struct or interface. You have to click on it to find out.
The entries in the index section should link to something. The index section isn't in itself a complete summary of the package or the names it contains. If we list the methods of an interface, it will link to the definition of the interface. If we list the fields of a struct, it will link to the definition of the struct. That doesn't seem helpful. Ian > On Mon, Dec 24, 2018 at 12:04 PM Ian Lance Taylor <i...@golang.org> wrote: >> >> On Mon, Dec 24, 2018 at 9:29 AM Mark Volkmann <r.mark.volkm...@gmail.com> >> wrote: >> > >> > IIUC, Kind is a method of both Type and Value. But the index near the top >> > of https://golang.org/pkg/reflect/ only shows it as a method of Value. If >> > you click on "type Type" in the index, it scrolls to the description of >> > that interface which includes the Kind method. >> > >> > Is it wrong that the index excludes the Kind method in the list of Type >> > methods? >> >> It is displayed that way because Value is a struct while Type is an >> interface. >> >> Ian > > > > -- > R. Mark Volkmann > Object Computing, Inc. -- 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.
