Thanks for volunteering! I think 2 is the correct approach here. Sam
On Fri, Jun 26, 2015 at 8:58 PM, Jordan Johnson <j...@fellowhuman.com> wrote: > Hi all, > > One thing I’ve noticed in working with Typed Racket is that some of the > libraries on the “Libraries Provided with Typed Racket” docs page have type > definitions that aren’t documented anywhere, but that ought to be visible to > TR programmers. Sometimes, I look at that docs page and think, “Gee, I’d be > happy to spend a little time writing docs for those types, if I knew where > to do it.” > > So, is there any planned idea of where the documentation for the TR-specific > parts of all those wrapper libraries currently in the typed-racket-more > package ought best to wind up? AFAICT there are at least three > possibilities: > > The wrappers eventually migrate to the libraries they wrap, and the docs > then have an obvious home there. > The wrappers stay where they are, and documentation for a wrapper lib goes > beneath its (require …) rectangle on the TR libs page linked above. > The wrapper libs get separate HTML files in the TR reference. > > > I don’t have a preference, but would gladly do some writing if the main TR > devs suggest where. > > Regards, > Jordan > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
