You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RAPIDS updated to C++17 a little over three years ago (here's cudf's). Since C++ standards are released every three years, we ought to be about on track to consider upgrading our builds to use C++20. C++20 is a pretty huge release with a lot of major new features like modules, concepts, and ranges, all of which we could make good use of in RAPIDS. Compiler support is tracked here. It seems like gcc has near-complete support for C++20 now (modules are still partial) so that shouldn't be a bottleneck any more.
The text was updated successfully, but these errors were encountered:
RAPIDS updated to C++17 a little over three years ago (here's cudf's). Since C++ standards are released every three years, we ought to be about on track to consider upgrading our builds to use C++20. C++20 is a pretty huge release with a lot of major new features like modules, concepts, and ranges, all of which we could make good use of in RAPIDS. Compiler support is tracked here. It seems like gcc has near-complete support for C++20 now (modules are still partial) so that shouldn't be a bottleneck any more.
The text was updated successfully, but these errors were encountered: