Details

    • Type: Bug
    • Status: Open
    • Priority: Blocker
    • Resolution: Unresolved
    • Affects Version/s: Scala 2.10.0, Scala 2.11.0
    • Fix Version/s: Backlog
    • Component/s: Reflection
    • Labels:
      None

      Description

      It seems like it's high time to generalize and unify our approach to various pieces of metadata under annotations.

      On the one hand, we have flags (https://issues.scala-lang.org/browse/SI-6267) and DocDefs (https://issues.scala-lang.org/browse/SI-7993) that can be represented as annotations. They can also be joined by visibility modifiers, associatedFile and maybe even attachments, giving us uniform way to store, query and update metadata on reflection artifacts.

      On the other hand, it seems that we can drastically simplify our annotations by replacing them with plain trees. We have to decide on the exact shape of those trees (at the moment, I like Denys's idea of translating `@foo(bar, baz)` into a typechecked invocation of `foo(bar, baz)` where `foo` can be whatever's in scope rather than `new foo(bar, baz)` where `foo` can only be a subclass of Annotation like it's done now) and on Java compatibility policy, but once we do that, everything is going to become so much simpler: https://groups.google.com/forum/#!topic/scala-internals/8v2UL-LR9yY

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                burmako Eugene Burmako
                Reporter:
                burmako Eugene Burmako
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: