-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
Type parameters better have defaults in the presence of Option #143
Labels
Comments
homu
added a commit
that referenced
this issue
Jan 9, 2016
Provide type parameter defaults for optional parameters Closes #143
Apparently, I've jumped the gun on this one. It looks like type parameter defaults on functions are going to be feature gated (rust-lang/rust#27336). |
What about using trait objects? Isn't the widget is a gtk pointer anyways? |
Trait objects don't work with the Are type parameter defaults stable now? |
No not stable yet |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This
requires jumping through hoops to pass
None
:There's not much we can do to help it at the moment, because default type parameters don't inform type inference yet. When that is fixed the following signature is going to be more ergonomic;
The text was updated successfully, but these errors were encountered: