Skip to content

Distributed actors (and actors) should be distinct semantic tokens #2709

Open
Feature
Open
Distributed actors (and actors) should be distinct semantic tokens#2709
Feature

Description

@ktoso
ktoso
opened on Jul 4, 2026

Description

  distributed actor Worker {
    distributed var num: Int { 2 }
    distributed func ping() {}
  }

textDocument/semanticTokens/full returns:

  • Worker: (class, [declaration])
  • num: (property, [declaration])
  • ping: (method, [declaration])

Nothing indicates any of these are distributed.

For what it's worth, even actor should be getting a distinct semantic token I think, because we may want to highlight actors differently; they're not just classes.

Activity

  1. ktoso
    added the
    Feature
    issue type on Jul 4, 2026

  2. ahoppen commented on Jul 6, 2026

    @ahoppen
    ahoppen
    on Jul 6, 2026
    Member

    actor is not a semantic token type specified in the LSP protocol. If we add a custom token type for that, then likely no editor would know about it, causing the actors to not be highlighted at all. Thus, I think highlighting them as classes is the correct choice for now. If anything, we might be able to add a custom modifier.

    @ktoso do you have an editor in mind in which you’d configure custom highlighting for actors?

  3. sean7218 commented on Jul 13, 2026

    @sean7218
    sean7218
    on Jul 13, 2026
    Contributor

    I would like to work on this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Feature

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions