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.

Sign up for GitHub

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

Jump to bottom

Detect type inference failures and use explicit types when necessary #49

Merged
merged 10 commits into from
Mar 20, 2015
Merged

Detect type inference failures and use explicit types when necessary #49

merged 10 commits into from
Mar 20, 2015

Conversation

EamonNerbonne
Copy link
Owner

This fixes issue 13.

@EamonNerbonne
Copy link
Owner Author

@dadhi I was hoping this might fix issue #13 without requiring explicit types all the time - thoughts?

@dadhi
Copy link
Collaborator

dadhi commented Mar 20, 2015

Yes, I also like inference more than long unnecessary specification, and if it is working (as I see from the tests), that's fine with me.
Thanks,
Maksim

EamonNerbonne added a commit that referenced this pull request Mar 20, 2015
@EamonNerbonne
Merge pull request #49 from EamonNerbonne/eamon/detect-type-inference…
49f65ad 
…-failures

Detect type inference failures and use explicit types when necessary
@EamonNerbonne EamonNerbonne merged commit 49f65ad into master Mar 20, 2015
@EamonNerbonne EamonNerbonne deleted the eamon/detect-type-inference-failures branch March 20, 2015 17:21
@EamonNerbonne EamonNerbonne mentioned this pull request May 5, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@dadhi dadhi

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@EamonNerbonne @dadhi