Re: [GSOC2020][Boost.uBLAS] C++20-ification of uBLAS

Cem Bassoy via ublas <[email protected]> Fri, 27 Mar 2020 10:46:14 +0100
Newsgroups gmane.comp.lib.boost.ublas
Message-ID <CADrR+FtE4cp0399eVuzwL+=sjEguGNY2TC1syL_pEDuxT=c+Eg@mail.gmail.com>
--===============1972924092329571234==
Content-Type: multipart/alternative; boundary="0000000000008cbafe05a1d2f950"

--0000000000008cbafe05a1d2f950
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks Ashar.

I would like you to also analyze the following proposal:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1385r5.pdf
What is your take on engine types. Let us discuss about that.

Best,
Cem

Am Fr., 20. M=C3=A4rz 2020 um 13:42 Uhr schrieb Ashar via ublas <
[email protected]>:

> Hi Cem,
>
> Thanks for the clarification. All my concerns and doubt about the proposa=
l
> are finished and we are good to go. I will be sharing the proposal soon
> here titled : "Boost.uBLAS: Stabilizing, Enhancing and C++20-ification".
> Each phase will have one of the thing mentioned here completed. During
> first phase, I will be stabilizing the code that we worked last year,
> notably the static_extent, sub tensor and other interfaces. Second phase
> will be enhancing which will involve producing a new matrix and vector ty=
pe
> based on tensor, Finally I would be implementing the C++20 concepts to
> replace all meta functions and restricting the template parameters. This
> will be as per your wish could be carried on a different branch.
>
> Regards
> Ashar
> _______________________________________________
> ublas mailing list
> [email protected]
> https://lists.boost.org/mailman/listinfo.cgi/ublas
> Sent to: [email protected]
>

--0000000000008cbafe05a1d2f950
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks Ashar. <br></div><div><br></div><div>I would l=
ike you to also analyze the following proposal: <a href=3D"http://www.open-=
std.org/jtc1/sc22/wg21/docs/papers/2020/p1385r5.pdf">http://www.open-std.or=
g/jtc1/sc22/wg21/docs/papers/2020/p1385r5.pdf</a></div><div>What is your ta=
ke on engine types. Let us discuss about that. <br></div><div><br></div><di=
v>Best,</div><div>Cem<br></div></div><br><div class=3D"gmail_quote"><div di=
r=3D"ltr" class=3D"gmail_attr">Am Fr., 20. M=C3=A4rz 2020 um 13:42=C2=A0Uhr=
 schrieb Ashar via ublas &lt;<a href=3D"mailto:[email protected]">ublas=
@lists.boost.org</a>&gt;:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Cem,</div><div><br></d=
iv><div>Thanks for the clarification. All my concerns and doubt about the p=
roposal are finished and we are good to go. I will be sharing the proposal =
soon here titled : &quot;Boost.uBLAS: Stabilizing, Enhancing and C++20-ific=
ation&quot;. Each phase will have one of the thing mentioned here completed=
. During first phase, I will be stabilizing the code that we worked last ye=
ar, notably the static_extent, sub tensor and other interfaces. Second phas=
e will be enhancing which will involve producing a new matrix and vector ty=
pe based on tensor, Finally I would be implementing the C++20 concepts to r=
eplace all meta functions and restricting the template parameters. This wil=
l be as per your wish could be carried on a different branch.</div><div><br=
></div><div>Regards</div><div>Ashar<br></div></div></div>
_______________________________________________<br>
ublas mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]=
t.org</a><br>
<a href=3D"https://lists.boost.org/mailman/listinfo.cgi/ublas" rel=3D"noref=
errer" target=3D"_blank">https://lists.boost.org/mailman/listinfo.cgi/ublas=
</a><br>
Sent to: <a href=3D"mailto:[email protected]" target=3D"_blank">cem.bass=
[email protected]</a><br>
</blockquote></div>

--0000000000008cbafe05a1d2f950--

--===============1972924092329571234==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline