Community
Participate
Working Groups
Trying to better understand the usage of ConditionalFlowInfo I stumbled upon a difference which looks unmotivated to me: When an AllocationExpression analyses its arguments, after each invocation the flowInfo is compressed using unconditionalInits(). In QualifiedAllocationExpression this call is missing. Looking at MessageSend where also the result of analysing the receiver is compressed in this way, the same may also apply to the enclosingInstance of a QAE. I checked for the origin of this inconsistency: it's present since the initial commit 1.1.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.