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

should "_Task_parallel _Call" be part of a function's type? #15

Open
nelsc opened this issue Dec 8, 2015 · 4 comments
Open

should "_Task_parallel _Call" be part of a function's type? #15

nelsc opened this issue Dec 8, 2015 · 4 comments
Assignees

Comments

@nelsc
Copy link
Contributor

nelsc commented Dec 8, 2015

No description provided.

@nelsc
Copy link
Contributor Author

nelsc commented Dec 8, 2015

Personally, I think that, if we are going to support this at all, we really need to make it an addition to the type system.

@phalpern
Copy link

phalpern commented Dec 8, 2015

I agree that it needs to be part of the type system.

@nelsc nelsc self-assigned this Jan 5, 2016
@nelsc
Copy link
Contributor Author

nelsc commented Jan 6, 2016

When I started looking into this, I rediscovered a paper I wrote and posted about 1.5 years ago, which was never discussed in a meeting:

http://wiki.edg.com/pub/CPLEX/MeetingSep082014/spawnspecifier.htm

@nelsc
Copy link
Contributor Author

nelsc commented Jan 11, 2016

There was general support for the direction of making "_Task _Call" a type qualifier. However, we want to double-check again the way Microsoft treats calling-convention specifiers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants