From fdacde606cf45e886aba8940f7ffdc320071dd73 Mon Sep 17 00:00:00 2001 From: Mateusz Pusz Date: Thu, 21 Dec 2023 12:25:10 +0100 Subject: [PATCH] docs: implicit point origin related erroneous case added to example in the interoperability chapter --- .../use_cases/interoperability_with_other_libraries.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/users_guide/use_cases/interoperability_with_other_libraries.md b/docs/users_guide/use_cases/interoperability_with_other_libraries.md index ec3fbed1..682743e2 100644 --- a/docs/users_guide/use_cases/interoperability_with_other_libraries.md +++ b/docs/users_guide/use_cases/interoperability_with_other_libraries.md @@ -271,9 +271,13 @@ The **mp-units** library comes with built-in interoperability with those types. quantity_point qp4 = my_origin + 1 * s; auto tp4 = to_chrono_time_point(qp4); // Compile-time Error (1) + + quantity_point qp5{1 * s}; + auto tp5 = to_chrono_time_point(qp5); // Compile-time Error (2) ``` 1. `my_origin` is not defined in terms of `chrono_point_origin`. + 2. `implicit_zeroth_point_origin` is not defined in terms of `chrono_point_origin`. Here is an example of how interoperability described in this chapter can be used in practice: