Skip to content

Removing a requirement in toi_promote which is confusing and unnece… #4507

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+3 −3
Open

Removing a requirement in toi_promote which is confusing and unnece… #4507

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
74d44f9
Removing a requirement in `toi_promote` which is confusing and unnece…
eernstg Sep 1, 2025
7e79ca7
Whitespace
eernstg Sep 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions resources/type-system/flow-analysis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -471,9 +471,9 @@ Definitions:
_The types in `p1` are known as the types of interest._
- Let `p2` be the set `p1 \ { provisionalType }` _(where `\` denotes set
difference)_.
- If the `written` type is in `p2`, and `written <: provisionalType`, then
`newPromotionChain` is `[...promotionChain, written]`. _Writing a value
whose static type is a type of interest promotes to that type._
- If the `written` type is in `p2` then `newPromotionChain` is
`[...promotionChain, written]`. _Writing a value whose static type is a
type of interest promotes to that type._
- _By precondition, `written <: declared` and `written <: T` for all types
in `promotionChain`. Therefore, `newPromotionChain` satisfies the
definition of a promotion chain, and is valid for declared type
Expand Down