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

Where do we get the info we need for TMS? #4

Open
moradology opened this issue Jul 27, 2017 · 0 comments
Open

Where do we get the info we need for TMS? #4

moradology opened this issue Jul 27, 2017 · 0 comments
Labels

Comments

@moradology
Copy link
Contributor

Interpreting TMS seems to require that we make some guarantees about coextension of computed sources. How, then, is such information provided? Some options:

  1. make the AST bigger and more complicated so that it can inform the interpreter of such things (this seems bad)
  2. assume the provider of sources is only providing tiles for apples to apples comparisons (dangerous, though currently the strategy of RFML)
  3. Create new instances of the interpreter with expectations for output and make sure that tile sources provide enough information for the interpreter to fulfill said expectations (this is likely the path)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant