-
Notifications
You must be signed in to change notification settings - Fork 0
perf: compute UIContext on prepare #29
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.
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 hidden or 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
panic!macro immediately terminates the current thread. While this can be useful in development to catch unexpected states, it's generally better to handle errors more gracefully in production code. Consider returning aResultwith an appropriate error message to allow the caller to handle the error case.Also, the error message is very specific and includes implementation details. It would be better to provide a more general error message that doesn't expose internal workings.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gemini-code-assist This branch is probably unreachable because the UI type parameter will not be decided without being set via the function(it also sets ctuf) or adding a type annotation. The user must know what they are doing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right that under normal, correct usage, this branch might be unreachable. However, in Rust,
panic!is generally reserved for unrecoverable errors or programmer bugs that indicate a fundamental flaw in the program's logic. For situations where an API contract might be violated by the caller (e.g.,cushion_to_uinot being set), returning aResultis the idiomatic way to signal an error that the caller can then handle gracefully.Even if the user 'must know what they are doing,' a
panic!will crash the thread, which is often undesirable in a larger application. Returning anErrallows the application to recover, log the issue, or present a user-friendly error message without terminating.Additionally, the original error message still contains internal details. A more general message would be beneficial regardless of whether it's a
panic!or anErr.