Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future Work: Special support for effects and handlers in the IDE #23

Open
b-studios opened this issue Apr 21, 2020 · 1 comment
Open
Assignees
Labels
area:lsp feature New feature or request

Comments

@b-studios
Copy link
Collaborator

b-studios commented Apr 21, 2020

Some unstructured notes about things we might want to support at some point:

Possible IDE features:

  • infer effects from effect holes
  • update effects (fix effects refactoring)
  • display inferred effects / types
  • what are better alternatives to stack traces?

Questions:

  • what effects are required by this function?
  • effect provenance: where does this effect come from? (racket like) -- since we already translate to capabilities, we can easily show this particular binding information to the user
  • what are potential handlers (call site analysis, called from)
  • given a handler: which calls to operations might be handled?
def bar(x: Int) = {
    ...
}

def foo(): Int / Print = <?
  val x = foo();
  x
?> // ?? =. <? () ?>

def bar() = {
    val position = 42
    position.<? { x => x + 1 } ?>
    ({ x => 42 })(5)
    ()
}
@b-studios b-studios added the feature New feature or request label Apr 21, 2020
@timmy-newtron timmy-newtron pinned this issue Nov 2, 2020
@timmy-newtron timmy-newtron unpinned this issue Nov 2, 2020
@b-studios
Copy link
Collaborator Author

This was addressed by @timmy-newtron in his BSc thesis, but sadly never merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:lsp feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants