rustdoc only show the type of a constant, not the actual value
I'm making a library in Rust and I've started writing documentation for it. I notice that on e.g. https://doc.rust-lang.org/std/primitive.u128.html, the values of constants such as u128::BITS are hidden, and only pub const BITS: u32 is displayed. However, when I run cargo doc on my computer for my library, the documentation page shows the values of all associated constants for a struct that I have defined.
There are other similar constants which use several lines of code to compute and so look quite ugly like this one. How can I change this so that the value of each constant is hidden?
I have now published this library and in the documentation on docs.rs this issue is no longer present, with the values of associated constants being hidden and an underscore displayed instead. So it only appears to be an issue when building documentation locally.
I'm not sure if this is a bug in rustdoc when running locally, or whether it is intentional to display the values of constants in development but hide them in production. However, because obviously the appearance of local documentation isn't so important, this is not really a problem anymore.
- How to set message size limit for actix websocket actorless?
- How to structure the type of a Rust object to share between threads
- How to navigate to Rust sources in VSCode?
- How to allocate a DST struct
- Is it possible to get the path from an opened file object in Rust?
- Selecting with Indexing is an anti-pattern in Polars: How to parse and transform (select/filter?) a CSV that seems to require so?
- thread '<unnamed>' panicked at assertion
- Why isn't the `+ 'static` on my `-> impl Future<...> + 'static` trait method respected?
- Dynamically sized struct in Arc
- Require in a Trait that all Iterators<Item = Self> implement a Trait
- Unable to create a local function because "can't capture dynamic environment in a fn item"
- How can I know if something is initialized in Rust?
- Satisfy trait C via trait A *or* B
- no targets specified in the manifest - either src/lib.rs, src/main.rs, a [lib] section, or [[bin]] section must be present
- Passing a variable into a Rust FnMut without having it turn into a FnOnce
- Custom deserializer to deserialize a HashMap over arbitrary types
- What are the semantics of an underspecified exact version pin in Cargo?
- How do you test functions that return Result?
- The from_utf8 Rust function cannot read some ASCII strings (invalid utf-8 sequence of 1 bytes)
- Can serde_json::to_writer_pretty indent with tabs rather than 2 spaces?
- rust compilation - failed to run custom build command for libseat-sys v0.1.7 - The system library libseat required by crate libseat-sys was not found
- How do I clone structs in Rust without using either Copy or Clone?
- Rust mismatch between input and output types of trait object
- Mutable app state in Tauri accessible from tauri::command
- Indexing a `HashMap<&String, V>` with `&str`
- How to convert a Vec<String> to an array of string slices?
- Does the core crate will implement a default trait for my struct and why the core crate does this?
- Can't bring mpsc receiver into iced.rs update logic
- Trouble getting rust lifetimes working for function mocking
- Rust-SIMD hello world