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

Allow usage and capture of 'cancellationToken' in lambdas and local functions #34708

Closed
jcouv opened this issue Apr 3, 2019 · 1 comment
Closed

Allow usage and capture of 'cancellationToken' in lambdas and local functions #34708

jcouv opened this issue Apr 3, 2019 · 1 comment
Assignees
@jcouv
Labels
Area-Compilers New Feature - Async Streams Async Streams
Milestone
16.1

Comments

@jcouv
Copy link
Member

jcouv commented Apr 3, 2019 •
edited
Loading

As part of the PR to add support for special cancellationToken variable (#34692), I blocked those scenarios temporarily to get the bulk of the feature working.

This issue is referenced in source and tests.

Should test:

  • in lambdas
  • in expression trees
  • in nested local functions (some being async-iterators and some not)

Relates to #24037 (async-streams umbrella)
@jcouv jcouv added this to the 16.1 milestone Apr 3, 2019
@jcouv jcouv self-assigned this Apr 3, 2019
@jcouv jcouv mentioned this issue Apr 3, 2019
Closed
10 tasks
@jcouv
Copy link
Member Author

jcouv commented Apr 18, 2019

We're dropping the special cancellationToken variable approach in favor of the [DefaultCancellation] token.

@jcouv jcouv closed this as completed Apr 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jcouv jcouv

Labels
Area-Compilers New Feature - Async Streams Async Streams
Projects
None yet
Milestone
16.1
Development

No branches or pull requests
1 participant
@jcouv