TaskCompletionSource and CancellationToken not implemented #790

Closed
johnwason opened this Issue Dec 22, 2015 · 1 comment

Projects

None yet

4 participants

@johnwason

TaskCompletionSource and CancellationToken are not currently implemented in the Bridge.NET library. These two classes are very important to async/await code and should be available. Note that CancellationToken is a structure. Issue #789 covers an issue with how structures are handled.

@DaniilVeriga DaniilVeriga added the defect label Dec 23, 2015
@DaniilVeriga DaniilVeriga added this to the 1.11 milestone Dec 23, 2015
@DaniilVeriga DaniilVeriga added feature and removed defect labels Dec 23, 2015
@DaniilVeriga
Contributor

Thank you for the request! We'll be investigating.

@vladsch vladsch added a commit that referenced this issue Jan 25, 2016
@vladsch vladsch [TEST] [#790] Update unit tests 7cc9b14
@vladsch vladsch added a commit that referenced this issue Feb 3, 2016
@vladsch vladsch [#790] Fix failed unit tests c15a946
@LeonidVeriga LeonidVeriga added a commit that referenced this issue Feb 6, 2016
@LeonidVeriga LeonidVeriga [TEST] [#790] Async test enhancement - avoid using .setTimeout(), use…
… task.ContinueWith() instead.
e959730
@LeonidVeriga LeonidVeriga added a commit that referenced this issue Feb 6, 2016
@LeonidVeriga LeonidVeriga [TEST] [#790] Promise test enhancement - avoid using .setTimeout(), u…
…se task.ContinueWith() instead.
fa42b16
@LeonidVeriga LeonidVeriga added a commit that referenced this issue Feb 6, 2016
@LeonidVeriga LeonidVeriga [TEST] [#790] Task test enhancement - avoid using .setTimeout(), use …
…task.ContinueWith() and Task.Run()instead.
fbaf0cb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment