Skip to content

opt-into copying annotations to exports #19516

Open
@bishabosha

Description

@bishabosha

prompted by #19509 (comment)_ in general it may be useful to copy annotations to exported methods, however for some it leads to broken behavior - such as tailrec. So perhaps it should be opt-in. Unless no annotations are copied, and there is proposed another mechanism for recovery of annotation information from the forwarded entity.

Compiler version

3.4.0-RC2

Info

The thing is that we will never know what should be the behavior for custom annotations.

The only holistic solution here is to have an @meta-based indication of what to do. This is the approach used to determine whether annotations should go to fields/getters/setters. It would also be appropriate to determine whether it should go to exports/bridges/etc.

Originally posted by @sjrd in #19509 (comment)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions