Date: Tue, 18 Jun 2024 17:09:47 +0200
Actually, the opposite ;-) (which is consistent with chrono).
More info here:
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p3045r1.html#operations-in-the-affine-space
.
Best
Mat
wt., 18 cze 2024 o 17:07 Ville Voutilainen <ville.voutilainen_at_[hidden]>
napisaĆ(a):
> On Tue, 18 Jun 2024 at 18:02, Mateusz Pusz <mateusz.pusz_at_[hidden]> wrote:
> >
> > I am not sure what you mean by "field types". Do you mean
> `year_month_day`?
> >
> > For now, we follow the `duration` and `time_point` design. C++
> developers have been exposed to it for many years now, and it is successful
> in most cases. This is why we believe that a similar abstraction with
> `quantity` and `quantity_point` should also prove OK. Many people claim
> that affine space abstraction is a mandatory feature of the units library.
>
> Well, if the design is similar, then you can't add a quantity to
> another or multiply a quantity with a quantity, you can do that only
> with quantity_points.
> Is that the current design?
>
More info here:
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p3045r1.html#operations-in-the-affine-space
.
Best
Mat
wt., 18 cze 2024 o 17:07 Ville Voutilainen <ville.voutilainen_at_[hidden]>
napisaĆ(a):
> On Tue, 18 Jun 2024 at 18:02, Mateusz Pusz <mateusz.pusz_at_[hidden]> wrote:
> >
> > I am not sure what you mean by "field types". Do you mean
> `year_month_day`?
> >
> > For now, we follow the `duration` and `time_point` design. C++
> developers have been exposed to it for many years now, and it is successful
> in most cases. This is why we believe that a similar abstraction with
> `quantity` and `quantity_point` should also prove OK. Many people claim
> that affine space abstraction is a mandatory feature of the units library.
>
> Well, if the design is similar, then you can't add a quantity to
> another or multiply a quantity with a quantity, you can do that only
> with quantity_points.
> Is that the current design?
>
Received on 2024-06-18 15:10:00