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.

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

Asserts and checks #18201

Merged
merged 3 commits into from
Sep 23, 2023
Merged

Asserts and checks #18201

merged 3 commits into from
Sep 23, 2023

Conversation

hrydgard
Copy link
Owner

@hrydgard hrydgard commented Sep 23, 2023

Some more. Also, removes a unused variable.

@hrydgard hrydgard added this to the v1.16.4 milestone Sep 23, 2023
@hrydgard hrydgard merged commit 7dc18a9 into master Sep 23, 2023
18 checks passed
@hrydgard hrydgard deleted the asserts-and-checks branch September 23, 2023 17:59
@@ -45,6 +45,7 @@ class PromiseTask : public Task {
template<class T>
class Promise {
public:
// Never fails.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(as long as you assume OOMs don't exist or exist as a separate catastrophe than failure.)

-[Unknown]

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, but we're kinda screwed in several other ways simultaneously then. That said, "Never fails" is always a bit of an overconfident comment to put - but the meaning here is that there's no need to check for null return.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants