fix: Exclude type information for “new object” allocations #3450
Conversation
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
davidcok
approved these changes
Feb 3, 2023
jtristan
approved these changes
Feb 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #3449
This PR fixes the verifier so that it does not assume any specific dynamic type of the object allocated by
new object. This is a special allocation that is supposed to allocate an object of an arbitrary type. (See section 14.1 of the reference manual.)The PR also improves the source location reported when a program attempts
new XwhereXis a non-class, non-objecttype.By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.