02:02 <winny> https://docs.racket-lang.org/riposte/

02:02 <winny> > ((uncaught-exception-handler) (*(+(*)(*(+(*)(*)(*)(*)(*))(+(*)(*)(*)(*)(*))(+(*)(*)(*)(*))))(+(*)(*)(*)(*)))) uncaught exception: 404

16:09 <simendsjo> I'm having problems finding what the best practices are for documenting racket code. I like inline documentation as I read the code, but it doesn't look like the racket way. Also, defproc needs a contract, so if I might have to copy/paste definitions between code and documentation? And what about migrating to racket/typed eventually? I cannot seem to find any good resources on documenting racket code unfortunately.

16:31 <vraid> soegaard: the macro expansion didn't work in untyped modules, so it made sense to keep the keyword form. otherwise it works great. thanks agian

16:31 <vraid> again*

19:09 <greghendershott> rudybot: doc scribble/srcdoc

19:09 <rudybot> greghendershott: your sandbox is ready

19:09 <greghendershott> rudybot: doc scribble/srcdoc

19:09 <rudybot> greghendershott: not found in any library's documentation: scribble/srcdoc

19:09 <rudybot> greghendershott: not found in any library's documentation: scribble/srcdoc

19:10 <greghendershott> simendsjo: You might like https://docs.racket-lang.org/scribble/srcdoc.html

19:12 <greghendershott> You might want to wrap that in something you find more convenient.

19:12 <greghendershott> What I did in one project: https://github.com/greghendershott/frog/blob/2bc070a60333e1316ff713f9b9b577a7c27e54b3/frog/private/define-doc.rkt#L9

19:12 <rudybot> https://teensy.info/wRkAB4uUt7

19:12 <greghendershott> Example uses: https://github.com/greghendershott/frog/search?q=define-doc&unscoped_q=define-doc

19:14 <greghendershott> Having said that, `src` submodules are relatively new, there aren't many examples I know of, and by far most people use separate .scrbl files.

19:14 <greghendershott> derp I meant `srcdoc` submodules

20:33 <simendsjo> greghendershott: Yes, I found your code earlier through a newsgroup post you wrote and got it working, but I had to add contracts/types. Most languages support inline documentation as it's very convenient while reading and writing code, so I would expect it to be possible in racket too without being too complicated.

21:09 <winny> did anybody notice that riposte documentation URL is a 404, i reported it to riposte, but i'm not certain if it's actually a r-l.org issue instead