feat: release the turbofish #31
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Unlike functions with anonymous generic arguments (foo: impl Bar), functions with named generic arguments can be called using the turbofish-notation `foo::<Baz>` in the case of the compiler unable to infer the type themself. IMHO, in library-methods, anonymous generics should be avoided. Hoewever, they are perfectly fine for internal methods and functions or in an initial implementation. In memory of Anna Harren.
|
I actually didn't know you couldn't use turbofish with impl Trait parameters, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unlike functions with anonymous generic arguments (foo: impl Bar), functions with named generic arguments can be called using the turbofish-notation
foo::<Baz>in the case of the compiler unable to infer the type themself. IMHO, in library-methods, anonymous generics should be avoided. Hoewever, they are perfectly fine for internal methods and functions or in an initial implementation.