Scala Buggabot

@hubertp said: I am not sure if the fix for #6358 will help because the translation for nested objects is slightly different from lazy val accessors. I have already struggled...

@retronym said: `-Yshow-syms` is pretty revealing. ```scala class M(val t: Int) extends AnyVal { def lazyString = { object X class Y () => {X; new Y} } } [[symbol...

@odersky said: If everything fails we need to disable lazy vals and objects in extension methods. But it would be exceeedingly ugly. The root cause in both is that the...

@paulp said: Since 5d9cde105e8 this fails in an orderly fashion: ``` test/files/pos/t6359.scala:3: error: implementation restriction: nested object is not allowed in value class This restriction is planned to be removed...

@gkossakowski said: Which means we should close this ticket?

@paulp said: Well, there ought to be a ticket to remove the implementation restriction.

@hubertp said: I thought Josh was going to create one, at least he said he would. I would prefer to leave this one open (possibly rename it) as it contains...

@retronym said: @Hubert: What's the plan for this one? It is currently marked for 2.10.1, is that realistic? Anything I can do to help?

@hubertp said: Last time I looked into this (which was more than a month ago) I got stuck on a weird behaviour of nested classes in a normal, non value...

Imported From: https://issues.scala-lang.org/browse/SI-9484?orig=1 Reporter: Bernhard Messerer (messi) Affected Versions: 2.11.7 See #2, #6583 Attachments: - [TestMain.scala](https://issues.scala-lang.org/secure/attachment/16802/TestMain.scala) (created on Sep 23, 2015 9:54:01 AM UTC, 608 bytes)