Skip to content

issue-982 : Assign TopType to ObjectType at end of TypeAssigner#997

Merged
stschott merged 3 commits intodevelopfrom
issue-982-tr-without-ls
Jul 30, 2024
Merged

issue-982 : Assign TopType to ObjectType at end of TypeAssigner#997
stschott merged 3 commits intodevelopfrom
issue-982-tr-without-ls

Conversation

@sahilagichani14
Copy link
Copy Markdown
Collaborator

assign TopType to ObjectType at the end of TypeAssigner so LocalNameStandardizer doesn't give exception after.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Please isolate the issue and provide a source/class file pair instead of a class from a different library.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I have added that test case as well, I will remove this class from a diff lib.

c = a;
} catch (ArithmeticException ex) {
}
System.out.println(a);
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

remove println from the testcases. It unnecessary blows up the tests

@stschott stschott merged commit ffe8a5f into develop Jul 30, 2024
@stschott stschott deleted the issue-982-tr-without-ls branch July 30, 2024 07:15
@sahilagichani14 sahilagichani14 changed the title assign TopType to ObjectType at end of TypeAssigner issue-982 : Assign TopType to ObjectType at end of TypeAssigner Jul 31, 2024
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.

[Bug]: TypeAssigner fails if LocalSplitter is not applied beforehand

3 participants