3 ms·
QuickBASIC works the same way. Rust doesn't really build its help documentation for "built-in" access in the programming environment (everything is web-based, e
by zozbot234 7y ago
QuickBASIC works the same way. Rust doesn't really build its help documentation for "built-in" access in the programming environment (everything is web-based, even "local" docs launch in a web browser) but examples are a first-class feature; they're reused as test cases.
- agumonkey 7y agoTalking about that, rust html docs gobs a whopping 400MB (2/3 of the install size IIRC). When compressed they're 22MB.
- zozbot234 7y agoRust and cargo are quite wasteful of disk space anyway, they should fix that first. 400MB is a drop in the bucket.
- cesarb 7y agoNot long ago, there was support on Firefox to directly open HTML pages within compressed files (through the jar: protocol). If that still existed, it would be an option to distribute the rust HTML docs within a compressed .jar file, and let the browser read directly from it.
- agumonkey 7y agoyeah that's a pity albeit there's still zcat
- adwn 7y ago> Rust [...] everything is web-based Correction: Rust's help and documentation is HTML-based, and getting a local, automatically updated copy is trivial. > even "local" docs launch in a web browser Uh, so what? Can you name a better format for programming language documentation that's also ubiquitously supported?
- zozbot234 7y ago> Can you name a better format for programming language documentation that's also ubiquitously supported? Info format. It's supported by Emacs, and Emacs is the most ubiquitous of IDE's.
- randomblast 7y ago> Emacs is the most ubiquitous of IDE's. Sorry, have you been in a coma for 30 years?
- SEJeff 7y agoYour question is rhetorical here, right?
- adwn 7y ago> Info format. I said "ubiquitously supported". There are several orders of magnitude difference between info format support and HTML support. > Emacs is the most ubiquitous of IDE's That's laughably wrong.
- blacksmith_tb 7y agoWell, it may be on everyone's machine (just type 'which emacs') but that hardly makes it the most commonly used IDE, which I think is what's hard to stomach.
- deleted 7y ago[deleted]
- thu2111 7y agoWell, JavaDoc is a mix of HTML and custom tag language based, whereas Kotlin moved to Markdown + some similar tags. Because HTML is a pain in the rear to write compared to Markdown and can't express everything you want concisely. Maybe you mean Rust's documentation is rendered to HTML. In which case, sure, but so what? Good docs can be rendered to non-HTML formats too, typically for IDEs to display quickly without needing to load a full browser.
- cerebellum42 7y agoEven though the Rust docs aren't built for this purpose first, in IntelliJ or CLion I can still press Ctrl + Q on a method and see the full method documentation with examples. I think what IntelliJ does is simply parse the doc comment for that method and then render the markdown contained in it in the little popup. The standard docs are built from those comments as well.