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

+1 For compiler safety. How does it make sense to make an API available that is guaranteed to be the wrong thing to use? The ideal experience is for BeginInvoke not to exist on core. #47510

Closed
zhyy2008z opened this issue Jan 27, 2021 · 4 comments
Closed

+1 For compiler safety. How does it make sense to make an API available that is guaranteed to be the wrong thing to use? The ideal experience is for BeginInvoke not to exist on core. #47510

zhyy2008z opened this issue Jan 27, 2021 · 4 comments
Labels
area-System.Runtime

Comments

@zhyy2008z
Copy link

+1 For compiler safety. How does it make sense to make an API available that is guaranteed to be the wrong thing to use? The ideal experience is for BeginInvoke not to exist on core.

Originally posted by @jnm2 in #16312 (comment)
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Jan 27, 2021
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@jnm2
Copy link
Contributor

jnm2 commented Jan 27, 2021

My self 5 years ago has even less tact than my current self, apparently. 🙄

@stephentoub
Copy link
Member

The C# compiler synthesizes a BeginInvoke method when you use the delegate keyword. Are you proposing it not? If so, this is an issue for dotnet/roslyn or dotnet/csharplang.

https://sharplab.io/#v2:EYLgtghgzgLgpgJwDQxASwDYB8ACAmARgFgAoHAZgAIATODOAcwnkpwBZKAxAe24AoAlAG4gA===

@zhyy2008z
Copy link
Author

zhyy2008z commented Jan 27, 2021 •
edited
Loading

@stephentoub Ok, I will propose a new issue for dotnet/roslyn.

@zhyy2008z zhyy2008z mentioned this issue Jan 27, 2021
Closed
@ghost ghost locked as resolved and limited conversation to collaborators Mar 3, 2021
@tannergooding tannergooding removed the untriaged New issue has not been triaged by the area owner label Jun 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-System.Runtime
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@stephentoub @zhyy2008z @maryamariyan @jnm2 @tannergooding