Add test coverage for class instance scope survival in conditional/loop blocks #1098
+58
−0
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.
Addresses review feedback requesting test coverage for class instances created in inner scopes (
se/enquanto) and assigned to outer-scope variables. This scenario is critical withReferenciaMontaoimplementation, where incorrect deallocation on scope exit could invalidate valid references.Tests Added
seblock scope test: Verifies instance created inside conditional remains accessible after block exitenquantoloop scope test: Verifies instance created inside loop remains accessible after iteration completesBoth tests confirm instance properties remain valid and accessible from the outer scope variable.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.