Fix Task<TResult> debug proxy Result behavior and rename from Future #123752
+4
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Task<TResult>'s debug proxy was showingdefault(TResult)for theResultproperty of faulted/cancelled tasks, misleading developers about actual behavior. The debugger should show that accessingResultwill throw.Changes
SystemThreadingTasks_FutureDebugView<TResult>→SystemThreadingTasks_TaskOfTResultDebugView<TResult>("Future" was an old name for "Task")Resultproperty to delegate directly tom_task.Resultinstead of returningdefaultfor non-success statesBefore:
public TResult? Result => m_task.Status == TaskStatus.RanToCompletion ? m_task.Result : default;After:
public TResult Result => m_task.Result;Now the debugger properly reflects the exception that would be thrown when accessing
Resulton a faulted task.Original prompt
Task<T>debug proxy is misleading aboutResultof a non-success task #123751✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.