• Anders429@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Hey, maybe this will actually lead to standardization of feature documentation? It’s been in terrible shape for years. The fact that optional dependencies and features have been treated nearly the same by cargo, but treated differently by crates.io, makes it useless for discovering features for crates. Up until now, my go-to method is to examine the Cargo.toml file directly, and if I can’t figure out what a feature does there I look directly at the source code.