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

api(eval): accept zero or one arguments in all evaluation functions #1431

Merged
merged 1 commit into from
Mar 20, 2020
Merged

api(eval): accept zero or one arguments in all evaluation functions #1431

merged 1 commit into from
Mar 20, 2020

Conversation

dgozman
Copy link
Contributor

@dgozman dgozman commented Mar 19, 2020

References #1348.

@dgozman dgozman marked this pull request as ready for review March 19, 2020 23:17
@JoelEinbinder
Copy link
Contributor

Did two passes over it and it looks fine.

I don't like that we have are losing the ability to pass more than one argument, but it is nice that we can add options objects to things now without fear.

I'd like to see this patch against once it is rebased on top of #1166. The types for it are important.

@dgozman dgozman merged commit 16c7a5b into microsoft:master Mar 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants