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

type parameter inference #45

Closed
graydon opened this issue Jun 22, 2010 · 1 comment
Closed

type parameter inference #45

graydon opened this issue Jun 22, 2010 · 1 comment
Labels
A-typesystem Area: The type system

Comments

@graydon
Copy link
Contributor

graydon commented Jun 22, 2010

Currently if you have a function f[T](T t) you have to call it with explicit
type parameters, such as f[int](10) or f[char]('a'). This is not generally
necessary given the restricted set of contexts in which we permit type
parameters; the type inference system should be able to infer parameters.

Implement this.

@pcwalton
Copy link
Contributor

Add automatic parameter instantiation. Closed by a7eeeb5.

mbrubeck pushed a commit to mbrubeck/rust that referenced this issue Oct 17, 2011
dlrobertson pushed a commit to dlrobertson/rust that referenced this issue Nov 29, 2018
Discuss unambiguous function call syntax
eddyb pushed a commit to eddyb/rust that referenced this issue Jun 30, 2020
This is necessary because of crate names containing dashes, as pointed
out in rust-lang#45.
bors bot referenced this issue in softdevteam/alloy Apr 29, 2021
45: Inline allocation calls r=ltratt a=jacob-hughes



Co-authored-by: Jake Hughes <jh@jakehughes.uk>
djtech-dev pushed a commit to djtech-dev/rust that referenced this issue Dec 9, 2021
tautschnig added a commit to jaisnan/rust-dev that referenced this issue Aug 20, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-typesystem Area: The type system
Projects
None yet
Development

No branches or pull requests

2 participants