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

think about blame #34

Open
cyrus- opened this issue Feb 7, 2018 · 1 comment
Open

think about blame #34

cyrus- opened this issue Feb 7, 2018 · 1 comment
Assignees

Comments

@cyrus-
Copy link
Member

cyrus- commented Feb 7, 2018

seems technically simple to add to the cast forms, and might have some benefits as far as debugging cast failures goes, but not sure what the relevant metatheoretic properties that we'd need to prove are -- need to do some research. @matthewhammer also has some general qualms about the entire notion. :)

@matthewhammer
Copy link
Member

matthewhammer commented Mar 12, 2018

Just to clarify a few points related to my position:

  1. The notion of blame as it appears in gradual typing seems to be striving to be a predicate about execution traces: Which execution trace(s) lead to the cast error in question?
  2. Rather than characterize these calling contexts or execution traces logically in some open-ended way, which would be very difficult, blame uses the notion of static program labels.
  3. In a "live programming" utopia, we'd have something richer than static program labels. :)

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

No branches or pull requests

3 participants