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

Rip out support for inferred return type in local functions #7832

Closed
gafter opened this issue Jan 7, 2016 · 2 comments
Closed

Rip out support for inferred return type in local functions #7832

gafter opened this issue Jan 7, 2016 · 2 comments
Labels
Area-Compilers Feature Request Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented
Milestone
2.0 (Preview 1)

Comments

@gafter
Copy link
Member

gafter commented Jan 7, 2016

The prototype for local functions (in the future branch) currently includes some support for inferring the return type. The LDM decided that we don't want that. Of course it would be possible to relax this in the future, but for the first iteration this is what we want.

Please remove the code and only support explicitly declared return types.
@gafter gafter added this to the 1.2 milestone Jan 7, 2016
@gafter gafter self-assigned this Jan 7, 2016
@AdamSpeight2008
Copy link
Contributor

What was the reason for this decision?

@gafter
Copy link
Member Author

gafter commented Jan 7, 2016

It isn't well-specified, it is a mess to implement, and it conflicts with the possibility of extending local functions to support forward reference (to local functions) in the future.

gafter added a commit to gafter/roslyn that referenced this issue Jan 13, 2016
@gafter
Remove support for inferring the return type of a local function.
9fdc7d9 
Fixes dotnet#7832
@gafter gafter mentioned this issue Jan 13, 2016
Merged
@gafter gafter added 4 - In Review A fix for the issue is submitted for review. Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented and removed 2 - Ready 4 - In Review A fix for the issue is submitted for review. labels Jan 13, 2016
@gafter gafter removed their assignment Jan 14, 2016
@gafter gafter modified the milestones: 2.0, 1.2 Jan 14, 2016
@gafter gafter closed this as completed Jan 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Compilers Feature Request Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented
Projects
None yet
Milestone
2.0 (Preview 1)
Development

No branches or pull requests
2 participants
@AdamSpeight2008 @gafter