Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 516029

Summary: type resolution problem with Stream.concat
Product: [Eclipse Project] JDT Reporter: Reto Urfer <reto.urfer>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: stephan.herrmann
Version: 4.6   
Target Milestone: ---   
Hardware: PC   
OS: Windows 10   
Whiteboard: stalebug
Attachments:
Description Flags
class CompilerProblemWithTypeResolution which shows the problem none

Description Reto Urfer CLA 2017-05-02 04:22:06 EDT
Created attachment 268107 [details]
class CompilerProblemWithTypeResolution which shows the problem

Since Neon.3 code which compiled correctly with Neon.2 has now o problem resolving the type. The problem also exists with the current Oxigen build.

It seems that the tyype of the output of Stream.concat is not correct and therefore also the result of the collector.

In case the two stream which should be concatenated are first each assigned to a local variable the type of the concatenation is correct and the code comopiles.
Comment 1 Sasikanth Bharadwaj CLA 2017-05-02 04:56:42 EDT
Compiles fine on master. Which oxygen build did you try it on? Could you try with a more recent one while I go look for the change that fixed this?
Thanks
Comment 2 Stephan Herrmann CLA 2017-05-02 07:01:50 EDT
FWIW, all Oxygen Milestone builds accept the program.
Comment 3 Reto Urfer CLA 2017-05-03 04:08:40 EDT
I had the problem with and Oxygen installation with Java9 support (instelled with a oomph setup using the updaet site http://download.eclipse.org/eclipse/updates/4.7-Y-builds).

I did now a complete reinstall of this installation and after rebuilding the test project it compiles now also in this environment. So it seems to be no problem anymore with Eclipse Oxygen.
Comment 4 Eclipse Genie CLA 2020-04-01 14:01:25 EDT
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.