From 58f07799e85776c7fa058618f23b67b0d4fe61ba Mon Sep 17 00:00:00 2001 From: Mateusz Pusz Date: Wed, 16 Oct 2024 17:18:19 +0200 Subject: [PATCH] docs: "Many shades of the same unit" extended with a note about the derived units order --- .../users_guide/framework_basics/systems_of_units.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/users_guide/framework_basics/systems_of_units.md b/docs/users_guide/framework_basics/systems_of_units.md index 0d70dd06..a922a406 100644 --- a/docs/users_guide/framework_basics/systems_of_units.md +++ b/docs/users_guide/framework_basics/systems_of_units.md @@ -92,6 +92,18 @@ prints: All of the above quantities are equivalent and mean exactly the same. +!!! note + + The above code example may give the impression that the order of components in a derived + unit is determined by the multiplication order. This is not the case. As stated in + [Simplifying the resulting expression templates](interface_introduction.md#simplifying-the-resulting-expression-templates), + to be able to reason about and simplify units, the library needs to order them in an + appropriate order. This will affect the order of components in a resulting type and + text output. + + Please refer to [our FAQ](../../getting_started/faq.md#why-derived-units-order-is-not-preserved-from-the-multiplication) + for more information. + ## Constraining a derived unit to work only with a specific derived quantity