How do you like code documentation inline in the source code vs. as separate guides, or how would you do it?

This page summarizes the projects mentioned and recommended in the original post on /r/ProgrammingLanguages

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  • docs.rs

    crates.io documentation generator

  • OTOH, source-code-generated-docs normalize how code docs are, like the rust docs.rs paradigm, so it sort of forces or encourages package creators/maintainers to write docs.

  • book

    The Rust Programming Language

  • doc.rust-lang.org/book: More of a "guides" thing than a source-code doc thing.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • Lua

    Lua is a powerful, efficient, lightweight, embeddable scripting language. It supports procedural programming, object-oriented programming, functional programming, data-driven programming, and data description.

  • I think Lua is a good example of doing documentation well. The source code is commented only as much as needed, mainly with brief comments about things that might not be obvious and a small number of longer explanations of how the architecture works (mainly relevant to developers). It also has a super nice feature that's surprisingly rare: each file has a very short line at the top that describes what the file is, so you don't have to guess based on the filename alone. The API is documented in a single HTML file on the website that has both the high level descriptions of the language and architecture, as well as documentation for each public-facing function. The docs are maintained by hand, but the API is mostly stable, so the docs don't need to change very often.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • How does Rust go “from” here “into” there

    2 projects | dev.to | 19 May 2024
  • Rust Book maintainer ignore user request to fix installation guide

    1 project | news.ycombinator.com | 17 May 2024
  • Help me stop hating rust

    2 projects | news.ycombinator.com | 24 Jan 2024
  • Advice Sought: Double down on Solidity dev or switch to Product?

    1 project | /r/CryptoCurrency | 6 Dec 2023
  • Systems programming - Rust

    1 project | /r/learnrust | 6 Nov 2023