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

refactor!: Remove tracking of "culprit" from Require methods #5739

Merged
merged 3 commits into from
Jul 11, 2024

Conversation

niloc132
Copy link
Member

@niloc132 niloc132 commented Jul 9, 2024

The string culprit as a marker for pointing to an issue in a stack trace has never appeared in a DHC issue, nor in DHC slack, and the last DHE slack message to use it in a mildly helpful way was more than two years ago.

This patch removes the functionality from RequirementFailure, and also removes any overload of a method in Require that would allow callers to customize the depth within the stack that should be marked.

Partial #188

@niloc132 niloc132 added this to the 0.36.0 milestone Jul 9, 2024
@niloc132 niloc132 requested a review from rcaudy July 9, 2024 19:48
@niloc132
Copy link
Member Author

niloc132 commented Jul 9, 2024

The first commit simplifies RequirementFailure to match AssertionFailure, and can stand alone even if we want to drop the second.

I checked Core+, and RequirementFailure is never explicitly used, nor are any of the overloads that take a depth param.

The patch presently increases the size of the file rather than shrinking it - I think I accidentally inlined something that was used in many places, probably one of the fail() overloads. I'll take a quick attempt at undoing that and rewrite the second commit.

It has never appeared in a DHC issue, nor in DHC slack, and the last DHE
slack message to use it in a mildly helpful way was more than two years
ago.
Copy link
Member

@rcaudy rcaudy left a comment

Choose a reason for hiding this comment

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

I visually scanned all of the refactoring changes, looks clean. Please run nightlies, just in case.

@niloc132
Copy link
Member Author

@niloc132 niloc132 merged commit 5970ebc into deephaven:main Jul 11, 2024
16 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jul 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants