Add clarifying note about nomenclature

There's no point in documenting everything as being an Orchard whizzbang.
We are in the `orchard` crate, so the context should be obvious. This
also fits with the standard Rust naming guideline of not duplicating
module names in type name prefixes (`foo::bar::BarThing`).
This commit is contained in:
Jack Grigg 2021-03-09 10:39:02 +13:00
parent 2462bb219b
commit f7cad7762a
1 changed files with 7 additions and 0 deletions

View File

@ -1,4 +1,11 @@
//! # orchard
//!
//! ## Nomenclature
//!
//! All types in the `orchard` crate, unless otherwise specified, are Orchard-specific
//! types. For example, [`Address`] is documented as being a shielded payment address; we
//! implicitly mean it is an Orchard payment address (as opposed to e.g. a Sapling payment
//! address, which is also shielded).
#![cfg_attr(docsrs, feature(doc_cfg))]
// Catch documentation errors caused by code changes.