Skip to content

Conversation

@janvorli
Copy link
Member

There was a mix of using assert and _ASSERTE in this file. The assert is a pain for local testing on Windows, as it pops out a dialog box when the assert fires.
This change unifies all of them to _ASSERTE.

There was a mix of using `assert` and `_ASSERTE` in this file. The
`assert` is a pain for local testing on Windows, as it pops out a
dialog box when the assert fires.
This change unifies all of them to `_ASSERTE`.
@janvorli janvorli self-assigned this Oct 30, 2025
@janvorli janvorli requested a review from BrzVlad as a code owner October 30, 2025 18:57
Copilot AI review requested due to automatic review settings October 30, 2025 18:57
@janvorli janvorli requested a review from kg as a code owner October 30, 2025 18:57
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @BrzVlad, @janvorli, @kg
See info in area-owners.md if you want to be subscribed.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR unifies assertion macros in the interpexec.cpp file by replacing all instances of assert with _ASSERTE to improve the Windows development experience by avoiding dialog popups during local testing.

  • Replaced 12 instances of assert with _ASSERTE throughout the file
  • Maintained identical assertion logic and conditions
  • Improved debugging experience for Windows developers

break;
default:
assert(!"Unimplemented or invalid interpreter opcode");
_ASSERTE(!"Unimplemented or invalid interpreter opcode");
Copy link
Member

Choose a reason for hiding this comment

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

This should probably be something other than asserte, it's not recoverable and should be a failure even in release builds

Copy link
Member Author

Choose a reason for hiding this comment

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

You are right, this should rather be a fail fast, as it it unrecoverable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants