[racket] How to document a package and access its documentation

From: Jay McCarthy (jay.mccarthy at gmail.com)
Date: Mon Aug 12 14:28:30 EDT 2013

Building documentation requires running Racket code, so only ring-0
packages can be trusted. BTW, the hope is that all packages will be
ring-0, unless they are on probation or deliberately malicious.


On Mon, Aug 12, 2013 at 12:23 PM, Asumu Takikawa <asumu at ccs.neu.edu> wrote:
> On 2013-08-12 12:05:00 -0600, Jay McCarthy wrote:
>> No, I'm not suggesting that. We already have a plan for how the
>> package catalog will show documentation: by building the real
>> documentation and showing it. You said that you don't want to wait for
>> that and want something else as a stop gap. I agree with all your
>> problems with this stop gap, which is why I intend to implement the
>> original idea.
> Great!
> Would this apply to all packages or to only ring-0 packages?
> Thanks,
> Asumu

Jay McCarthy <jay at cs.byu.edu>
Assistant Professor / Brigham Young University

"The glory of God is Intelligence" - D&C 93

Posted on the users mailing list.