-
Notifications
You must be signed in to change notification settings - Fork 136
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Using custom `thiserror` errors instead of `Box<dyn Error>`, closes #285 This removed the use of `Result` as a return type for many functions, including `RenderContext::new()`. This "could" fail when no backend feature is activated for wgpu, but because we don't vendor them, this should never happen. (also there is no failable version of this function) I also had to make a `RendererError` which I totally hate, but the problem here is that without the `wgpu-profiler` feature this function never fails, so should I remove the `Result` and just unwrap for the `GpuProfiler`? There are still many unwraps, which may(?) still be handled correctly with errors, but for most of them I'm not sure. They are in many functions which had `Result` return types but still, `unwrap` was called, so was it intention? --------- Co-authored-by: Kaur Kuut <[email protected]>
- Loading branch information
Showing
6 changed files
with
140 additions
and
108 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.