Skip to content

[SE-0553] Explain intended use and pitfalls of observing a task identifier - #3539

Merged
jckarter merged 1 commit into
swiftlang:mainfrom
hassila:se-0553-intended-use
Oct 13, 2026
Merged

jckarter merged 1 commit into
swiftlang:mainfrom
hassila:se-0553-intended-use

Conversation

@hassila

@hassila hassila commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

The acceptance of SE-0553 asked the authors to clearly explain the intended use cases and potential pitfalls for observing a task identifier.

Adds a short subsection at the top of Detailed design that covers observing undocumented task structure, cancellation shields, identifiers not being handles, and side-table eviction, and point to it from the summary.

This is documentation only; no API or semantic changes.

…ifier

The acceptance of SE-0553 asked the authors to clearly explain the
intended use cases and potential pitfalls for observing a task
identifier. Add a short subsection at the top of Detailed design that
covers observing undocumented task structure, cancellation shields,
identifiers not being handles, and side-table eviction, and point to it
from the summary. Documentation only; no API or semantic change.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@rjmccall rjmccall added content change Content change to an existing document LSG Contains topics under the domain of the Language Steering Group labels Oct 12, 2026
@jckarter
jckarter merged commit e06222e into swiftlang:main Oct 13, 2026
@hassila
hassila deleted the se-0553-intended-use branch October 13, 2026 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content change Content change to an existing document LSG Contains topics under the domain of the Language Steering Group

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants