flush_and_throw()
Open
api: breaking
feature request
refactoring
- Dominant language
- C++
- Stars
- 161
- Forks
- 59
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 7
Description
With *deferred` flush type (#484), it is probably be a good idea to control which parts of the API are allowed to `throw`.
If we ever need or want to refactor this, the SYCL/DPC++ `::wait_and_throw()` construct and its user-defined error handlers are a nice design pattern.
The question is what how to properly design this if we simplify our API to allow synchronous access #484.
Contributor guide
Assessment
This issue has not been assessed yet.