Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[wishlist] Make Matthew's doc-define from ClojureWest keynote real #60

Open
spdegabrielle opened this issue Jul 22, 2019 · 6 comments
Open

Comments

@spdegabrielle
Copy link
Sponsor Member

from Wishlist of backwards incompatible things for a future Racket2. #33

@pmatos
Copy link

pmatos commented Jul 24, 2019

Is there a link to this reference/video?

@sorawee
Copy link
Contributor

sorawee commented Jul 24, 2019

@spdegabrielle
Copy link
Sponsor Member Author

slide 149:

In-Source Scribble Documentation

Screenshot 2019-07-24 at 19 42 04

@zlee-personal
Copy link

One thing I like about python is it's docstring system and help function. Scribble is great for documenting a library, but not so great for describing helper functions in a file that don't get exported. Most people just use comments, but we may benefit from having a more standard way of describing functions, perhaps available at runtime with something similar to help. I would enjoy having a tooltip pop up for a function, even one in the same file. Using scribble may be difficult for supporting tooltips (maybe), so maybe there could be a simple docstring in source, while scribble maintains it's html based interface with the user.

@benknoble
Copy link

Clojure's define forms allow arbitrary metadata to be attached to a symbol in a map: if racket and/or rhombus had something similar, it could be used for standard things (docs, types, contracts, what have you) and also for more interesting things (which I have not dreamt of).

@diego-crespo
Copy link

If we use scribble would that mean it would be possible to have executable code blocks within the documentation like Rust's Documentation tests? If so I think that would be great for the same reasons outlined on that page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants