Topic: Why do we include a Matrix and Vector class into the
Author: Jakob Riedle <jakob.riedle@gmail.com>
Date: Fri, 9 Jun 2017 04:15:02 -0700 (PDT)
Raw View
------=_Part_1054_557559726.1497006902246
Content-Type: multipart/alternative;
boundary="----=_Part_1055_1644072671.1497006902246"
------=_Part_1055_1644072671.1497006902246
Content-Type: text/plain; charset="UTF-8"
Hello Folks,
concerning Proposal P0267R1-4
<http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0267r4.pdf> (the
proposed 2D Graphics extension):
Recently stated the question, whether there is any interest in something
like a matrix/vector/tensor class extension.
The Consensus there was, that because we are confronted with the opinions
of a bunch of different stakeholders,
we should first approach the concept of Matrices from a "conceptional"
perspective before we even think about a specific implementation.
That means, we should first come up with a set of *Concepts *that provide
interfaces for the idea of multidimensional Arrays.
Now what is being done in P0267R1-4
<http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0267r4.pdf> is
the exact opposite of that:
Come up with an arbitrary, highly context dependent Matrix class that is
not reusable for anyone but the few people that want to work with 2D
Graphics.
I have the strong feeling that this is absolutely not desirable from a
standpoint of standardization:
*We want a C++ standard Library that is consistent in itself and does not
reinvent the wheel for every specific extension it gets.*
Please let me know your opinions on this!
Cheers and have a nice weekend,
Jakob
--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/7e3ee19d-f758-4d38-a015-0c474424073d%40isocpp.org.
------=_Part_1055_1644072671.1497006902246
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hello Folks,<div><br></div><div>concerning <a href=3D"http=
://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0267r4.pdf">Proposal P=
0267R1-4</a>=C2=A0(the proposed 2D Graphics extension):<br><br></div><div>R=
ecently stated the question, whether there is any interest in something lik=
e a matrix/vector/tensor class extension.</div><div>The Consensus there was=
, that because we are confronted with the opinions of a bunch of different =
stakeholders,</div><div>we should first approach the concept of Matrices fr=
om a "conceptional" perspective before we even think about a spec=
ific implementation.</div><div><br></div><div>That means, we should first c=
ome up with a set of <i>Concepts </i>that provide interfaces for the idea o=
f multidimensional Arrays.</div><div><br></div><div><br></div><div>Now what=
is being done in=C2=A0<a href=3D"http://www.open-std.org/jtc1/sc22/wg21/do=
cs/papers/2017/p0267r4.pdf">P0267R1-4</a>=C2=A0is the exact opposite of tha=
t:</div><div>Come up with an arbitrary, highly context dependent Matrix cla=
ss that is not reusable for anyone but the few people that want to work wit=
h 2D Graphics.</div><div><br></div><div><br></div><div>I have the strong fe=
eling that this is absolutely not desirable from a standpoint of standardiz=
ation:</div><div><b>We want a C++ standard Library that is consistent in it=
self and does not reinvent the wheel for every specific extension it gets.<=
/b></div><div><br></div><div><br></div><div>Please let me know your opinion=
s on this!</div><div><br></div><div>Cheers and have a nice weekend,</div><d=
iv>Jakob</div></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/7e3ee19d-f758-4d38-a015-0c474424073d%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/7e3ee19d-f758-4d38-a015-0c474424073d=
%40isocpp.org</a>.<br />
------=_Part_1055_1644072671.1497006902246--
------=_Part_1054_557559726.1497006902246--
.