Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrating to C++20 #82

Open
marty1885 opened this issue Sep 14, 2019 · 2 comments
Open

Migrating to C++20 #82

marty1885 opened this issue Sep 14, 2019 · 2 comments
Labels
enhancement New feature or request need discussion need some discussion

Comments

@marty1885
Copy link
Member

(When C++20 finally get released and compilers got support of it) I think we should move to C++20, making a lot of stuff easier:

  • No more "blablabal" + std::to_string(foo) + "blablabla" + std::to_string(bar)
    • string formatting solves the problem
  • Contracts, making the code faster
  • etc...
@marty1885 marty1885 added enhancement New feature or request need discussion need some discussion labels Sep 14, 2019
@marty1885
Copy link
Member Author

marty1885 commented Nov 24, 2019 •
edited

We could also replace the hacky source code JIT in OpenCLBackend with std::format this way.

@marty1885
Copy link
Member Author

marty1885 commented Jan 19, 2020 •
edited

The std::source_location feature could also improve our error message (and et_error doesn't need to be a macro)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request need discussion need some discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@marty1885