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

Issue 13702 - One missed 'may cause GC allocation' error message #5007

Merged
merged 1 commit into from Feb 2, 2016

Conversation

9rnsr
Copy link
Contributor

@9rnsr 9rnsr commented Sep 1, 2015

@@ -1791,13 +1791,14 @@ public:
fbody = new CompoundStatement(Loc(), fbody, s);
}
}
if (returns && !fbody.isErrorStatement())
if (returns)
Copy link
Member

Choose a reason for hiding this comment

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

Do we pay for the extra checks with slightly less performance in case this is done during speculative evaluations? Maybe just produce the complete @nogc coverage when not gagged.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry for late reply. I think, we should have same semantic analysis behavior with/without gagging. Branching analysis process depending on global.gag would be a cause of bug.

@dlang-bot
Copy link
Contributor

Fix Bugzilla Description
13702 One missed 'may cause GC allocation' error message

@ibuclaw
Copy link
Member

ibuclaw commented Feb 1, 2016

This is a 2.066 regression!

@ibuclaw
Copy link
Member

ibuclaw commented Feb 1, 2016

Auto-merge toggled on

ibuclaw added a commit that referenced this pull request Feb 2, 2016
Issue 13702 - One missed 'may cause GC allocation' error message
@ibuclaw ibuclaw merged commit 1a40790 into dlang:master Feb 2, 2016
@9rnsr 9rnsr deleted the fix13702 branch February 2, 2016 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants