Does uBLAS embrace C++ Core Guidelines?
Sean Reilly via ublas <[email protected]> Sat, 2 Jan 2021 13:00:20 -0500
| Newsgroups | gmane.comp.lib.boost.ublas |
|---|---|
| Message-ID | <CAJAKk0USLpsRpW8Zn4gdeP-tUe=jP2q4WapXH=m5hQ8EuBetTw@mail.gmail.com> |
--===============7817676155668791410== Content-Type: multipart/alternative; boundary="000000000000f99ef505b7eea13d" --000000000000f99ef505b7eea13d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I=E2=80=99ve been away from C++ for a quite few years, and it seems like a = lot has happened to my old friend C++98. As I start to dive into C++17 and beyond, I=E2=80=99m curious about the C++ community=E2=80=99s adoption of the C++ C= ore Guidelines and enforcement tools like clang-tidy. The uBLAS community is of particular interest to me, because the things we do focus on innovative use of language features to squeeze numerical performance out of C++ and not the typical GUI or network application efforts of so many other projects. To what extent is uBLAS embracing the Core ideal? Sean Reilly --000000000000f99ef505b7eea13d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I=E2=80=99ve been away from C++ for a quite few years, and it seems like a = lot has happened to my old friend C++98. As I start to dive into C++17 and = beyond, I=E2=80=99m curious about the C++ community=E2=80=99s adoption of t= he C++ Core Guidelines and enforcement tools like clang-tidy. The uBLAS com= munity is of particular interest to me, because the things we do focus on i= nnovative use of language features to squeeze numerical performance out of = C++ and not the typical GUI or network application efforts of so many other= projects.=C2=A0<div dir=3D"auto"><br></div><div dir=3D"auto">To what=C2=A0= extent is uBLAS embracing the Core ideal?</div><div dir=3D"auto"><br></div>= <div dir=3D"auto">Sean Reilly</div> --000000000000f99ef505b7eea13d-- --===============7817676155668791410== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline