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

Inferable types #66

Open
lucaswoj opened this issue Feb 25, 2015 · 1 comment
Open

Inferable types #66

lucaswoj opened this issue Feb 25, 2015 · 1 comment
Assignees

Comments

@lucaswoj
Copy link
Contributor

Some backends are able to infer ideal values for different parameters. We want to represent this behavior as a higher order type, Inferrable<T> (though perhaps notated differently in our front-end)

We need to decide how these types will be represented in our front-end language

  1. Inferable(T)
  2. @inferrable T
  3. T(inferable: true)

@lucaswoj likes 3 best right now... It would be a primitive attribute available on all types, i.e. (Boolean(inferable: true))

and how this should be represented in the front end.

@mtrberzi says the implementation of this feature is somewhat urgent for our clients

@lucaswoj
Copy link
Contributor Author

Actually, I think I like option 2 better now

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

2 participants