Scala Programming Language
  1. Scala Programming Language
  2. SI-6921

"no-symbol does not have an owner" with Scala 2.10 (named args side effects on trees)

    Details

      Description

      I'm attempting upgrade from 2.9.2 to 2.10. Code that previously compiled cleanly is now triggering the error "no-symbol does not have an owner" (I'll attach the full output, rather than pasting it in).

      I've tried to figure out where the failure was introduced, and I have found that the code compiles successfully at 2.10.0-M1, but the error occurs at 2.10.0-M2.

      I don't have a small repro, and I think that I'm not able to share the entire project that hits this problem. I recognise that this is not ideal! I'll play around a bit to see if I can get a smaller repro; if I come up with something that I can share then I will do so. Please advise if there's anything else I can do to help out.

      1. compile.txt
        102 kB
        David Hotham
      2. scala-bug-sbt-last.txt
        900 kB
        Andreas W

        Issue Links

          Activity

          Hide
          Andreas W added a comment -

          I have attached the output of "sbt> last". Hope it helps. I will attempt the isolation, but I can't spend more than a couple of hours on it, so can't guarantee success.

          Show
          Andreas W added a comment - I have attached the output of "sbt> last". Hope it helps. I will attempt the isolation, but I can't spend more than a couple of hours on it, so can't guarantee success.
          Hide
          Andreas W added a comment -

          As requested, I have opened a new issue: https://issues.scala-lang.org/browse/SI-7223

          Show
          Andreas W added a comment - As requested, I have opened a new issue: https://issues.scala-lang.org/browse/SI-7223
          Hide
          Jason Zaugg added a comment -

          Lukas: I can make the problem go away with a duplicate. https://github.com/retronym/scala/compare/ticket/7239

          What are the downsides of this? Can this introduce other problems?

          Show
          Jason Zaugg added a comment - Lukas: I can make the problem go away with a duplicate . https://github.com/retronym/scala/compare/ticket/7239 What are the downsides of this? Can this introduce other problems?
          Hide
          Lukas Rytz added a comment -

          I guess the downside is that it's a bit of a band-aid solution that has to be applied in many places - we know what we should do instead (make typed non-destructive), but that's more involved. Other than that duplicating is what I would have done as well, I don't think there are any problems with it.

          Show
          Lukas Rytz added a comment - I guess the downside is that it's a bit of a band-aid solution that has to be applied in many places - we know what we should do instead (make typed non-destructive), but that's more involved. Other than that duplicating is what I would have done as well, I don't think there are any problems with it.
          Show
          Jason Zaugg added a comment - https://github.com/scala/scala/pull/2253

            People

            • Assignee:
              Jason Zaugg
              Reporter:
              David Hotham
            • Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development