Incorrect errors shown in the editor when object defined with same name as case class

[scabug]

The presentation compiler seems to have issues when an object is defined with the same name as a case class.

Steps to reproduce:

(1) Create a file Foo.scala:

package test

object Foo {
  
}
case class Foo(t: String) {

}

(2) Open editor

(3) Notice that the editor shows two incorrect errors (construction definition not allowed here and constructor Foo is defined twice).

The file is actually compiled fine and nothing is shown in the Problems view. scalac also handles the file fine:

/opt/scala-2.8.0.Beta1-RC8/bin/scalac test/Foo.scala

[scabug]

Imported From: https://issues.scala-lang.org/browse/SI-2926?orig=1
Reporter: @ijuma

[scabug]

@milessabin said:
Interestingly reordering the object and class definitions makes the error go away.

[scabug]

@milessabin said:
As does changing the class to a vanilla class.

[scabug]

@ijuma said:
Interesting that reordering fixes the issue. I'll use that workaround. :)

I believe the issue is related to the fact that a companion object is created for case classes, so it doesn't surprise me that the problem goes away with a vanilla class.

[scabug]

@odersky said:
(In r20625) Attempt to fix #2926 (companion object of case class problem in Eclipse)

[scabug]

@milessabin said:
Unfortunately the problem is still present after r20625.

[scabug]

@odersky said:
(In r20634) Second attempt to fix #2926. Reverted first attempt. review by milessabin.

[scabug]

@milessabin said:
This looks very, very good (and fixes a lot of the residual case of #2767 as well).

Unfortunately tweaking the example slightly gets the originally reported error back,

package test

object Foo2 {
  object Foo {
  
  }
  case class Foo(t: String) {

  }
}

[scabug]

@odersky said:
I'll look at the remaining problem tomorrow.

[scabug]

@odersky said:
Should be fixed by now.

[scabug]

@ijuma said:
I can confirm that both cases now work.