Skip to content
This repository was archived by the owner on Sep 1, 2020. It is now read-only.
This repository was archived by the owner on Sep 1, 2020. It is now read-only.

Using type aliases with Symbol literals across projects crashes compiler. #181

Open
@lJoublanc

Description

@lJoublanc

When referring to a type alias defined in another project, the compiler crashes with errors like

[error] (b/compile:compileIncremental) malformed Scala signature of package at 139; bad constant tag: 37

I've created a minimal project to demonstrate this behaviour. Basically, define type MyOption = Option['mysymbol] in one project and refer to it in another causes a compiler crash. You can work around this if you copy the definition to the dependent project.

This only occurs when using Symbol type literals, so changing the type literal to a string "mysymbol" removes the error. (As shapeless uses Symbols for it's labels this is a problem though).

I can also see this is not reproducible in lightbend 2.13 branch (uncomment this in build.sbt to check).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions