Skip to content

@unroll should only apply to final or effectively final methods (300USD Bounty) #12

@lihaoyi

Description

@lihaoyi

From the maintainer Li Haoyi: I'm putting a 300USD bounty on this issue, payable by bank transfer on a merged PR implementing this.

See https://github.com/orgs/com-lihaoyi/discussions/6 for other bounties and the terms and conditions that bounties operate under


Following the final implementation of scala/improvement-proposals#78, we should only allow @unroll on methods that are final, or on an object (which is final), or on a final class.

@unroll on constructors and case classes are not affected, since the <init> and apply companion methods are already final

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions