fix: LA support fixed

docs/usage.rst

@@ -146,8 +146,8 @@ Specifies how :ref:`design/downcasting:The Downcasting Facility` works:
 Conan Configuration Properties
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-build_all
-+++++++++
+user.build:all
+++++++++++++++
 
 **Values**: ``True``/``False``
 
@@ -158,14 +158,24 @@ To support this it requires some additional Conan build dependencies described i
 `Repository Structure and Dependencies`_.
 It also runs unit tests during Conan build (unless ``tools.build:skip_test`` configuration property is set to ``True``)
 
-skip_docs
-+++++++++
+user.build:skip_la
+++++++++++++++++++
 
 **Values**: ``True``/``False``
 
 **Defaulted to**: ``False``
 
-If `build_all`_ is enabled, among others, Conan installs the documentation generation dependencies (i.e. doxygen) and
+If `user.build:all`_ is enabled, among others, Conan installs the external `wg21-linear_algebra<https://conan.io/center/wg21-linear_algebra>`_
+dependency and enables compilation of linear algebra based usage examples. Such behavior can be disabled with this option.
+
+user.build:skip_docs
+++++++++++++++++++++
+
+**Values**: ``True``/``False``
+
+**Defaulted to**: ``False``
+
+If `user.build:all`_ is enabled, among others, Conan installs the documentation generation dependencies (i.e. doxygen) and
 turns on the project documentation generation. Such behavior can be disabled with this option.
 
 CMake Options
@@ -181,6 +191,16 @@ UNITS_AS_SYSTEM_HEADERS
 Exports library as system headers.
 
 
+UNITS_BUILD_LA
+++++++++++++++
+
+**Values**: ``ON``/``OFF``
+
+**Defaulted to**: ``ON``
+
+Enables building code depending on the linear algebra library.
+
+
 UNITS_BUILD_DOCS
 ++++++++++++++++
 
@@ -414,8 +434,8 @@ In case you would like to build all the source code (with unit tests and example
 you should:
 
 1. Use the *CMakeLists.txt* from the top-level directory.
-2. Run Conan with `build_all`_ = ``True``
-   (use ``-o build_docs=False`` if you want to skip the documentation generation).
+2. Run Conan with `user.build:all`_ = ``True``
+   (use ``-c user.build:skip_docs=True`` if you want to skip the documentation generation).
 
 .. code-block:: shell
 
@@ -443,7 +463,7 @@ In case you would like to build the project's documentation, you should:
 
 1. Use the *CMakeLists.txt* from the top-level directory.
 2. Obtain Python dependencies.
-3. Run Conan with `build_all`_ = ``True``.
+3. Run Conan with `user.build:all`_ = ``True``.
 
 .. code-block:: shell
 

docs/use_cases/linear_algebra.rst

@@ -14,7 +14,7 @@ enough to be used with other Linear Algebra libraries existing on the market.
     or `Conan <https://conan.io/center/wg21-linear_algebra>`_.
     Also, to simplify the examples all of them assume::
 
-        using namespace std::math;
+        using namespace STD_LA;
 
 
 Linear Algebra of Quantities
@@ -27,16 +27,16 @@ The official :term:`quantity` definition states:
 
 So the most common use case would be to create a vector or matrix of quantities::
 
-    fs_vector<si::length<si::metre>, 3> v = { 1 * m, 2 * m, 3 * m };
-    fs_vector<si::length<si::metre>, 3> u = { 3 * m, 2 * m, 1 * m };
-    fs_vector<si::length<si::kilometre>, 3> t = { 3 * km, 2 * km, 1 * km };
+    fixed_size_column_vector<si::length<si::metre>, 3> v = { 1 * m, 2 * m, 3 * m };
+    fixed_size_column_vector<si::length<si::metre>, 3> u = { 3 * m, 2 * m, 1 * m };
+    fixed_size_column_vector<si::length<si::kilometre>, 3> t = { 3 * km, 2 * km, 1 * km };
 
 Having such definitions we can perform full dimensional analysis operations for the operations
 allowed by the Linear Algebra rules. For example::
 
     std::cout << "v + u     = " << v + u << "\n";
     std::cout << "v + t     = " << v + t << "\n";
-    std::cout << "t[m]      = " << fs_vector<si::length<si::metre>, 3>(t) << "\n";
+    std::cout << "t[m]      = " << fixed_size_column_vector<si::length<si::metre>, 3>(t) << "\n";
     std::cout << "v * u     = " << v * u << "\n";
     std::cout << "2 * m * v = " << 2 * m * v << "\n";
 
@@ -66,9 +66,9 @@ types provided to a `quantity` class template.
 
 With this the above vector definitions can be rewritten as follows::
 
-    si::length<si::metre, fs_vector<int, 3>> v(fs_vector<int, 3>{ 1, 2, 3 });
-    si::length<si::metre, fs_vector<int, 3>> u(fs_vector<int, 3>{ 3, 2, 1 });
-    si::length<si::kilometre, fs_vector<int, 3>> t(fs_vector<int, 3>{ 3, 2, 1 });
+    si::length<si::metre, fixed_size_column_vector<int, 3>> v(fixed_size_column_vector<int, 3>{ 1, 2, 3 });
+    si::length<si::metre, fixed_size_column_vector<int, 3>> u(fixed_size_column_vector<int, 3>{ 3, 2, 1 });
+    si::length<si::kilometre, fixed_size_column_vector<int, 3>> t(fixed_size_column_vector<int, 3>{ 3, 2, 1 });
 
 Now the same code doing basic Linear Algebra operations will provide the following
 output: