Initial Lanes implementation

Initial Lanes implementation

Initial Lanes implementation

[EXTREMELY WIP] Initial lanes implementation

[EXTREMELY WIP] Initial lanes implementation

[EXTREMELY WIP] Initial lanes implementation

[EXTREMELY WIP] Initial lanes implementation

[EXTREMELY WIP] Initial lanes implementation

[EXTREMELY WIP] Initial lanes implementation

Unhide Suspense trees without entanglement When a Suspense boundary is in its fallback state, you cannot switch back to the main content without also finishing any updates inside the tree that might have been skipped. That would be a form of tearing. ...

Unhide Suspense trees without entanglement When a Suspense boundary is in its fallback state, you cannot switch back to the main content without also finishing any updates inside the tree that might have been skipped. That would be a form of tearing. ...

SuspenseList: Reschedule at same priority SuspenseList progressively renders items even if the list is CPU bound, i.e. it isn't waiting for missing data. It does this by showing a fallback for the remaining items, committing the items in that have alr...

SuspenseList: Reschedule at same priority SuspenseList progressively renders items even if the list is CPU bound, i.e. it isn't waiting for missing data. It does this by showing a fallback for the remaining items, committing the items in that have alr...

Unhide Suspense trees without entanglement When a Suspense boundary is in its fallback state, you cannot switch back to the main content without also finishing any updates inside the tree that might have been skipped. That would be a form of tearing. ...

Unhide Suspense trees without entanglement When a Suspense boundary is in its fallback state, you cannot switch back to the main content without also finishing any updates inside the tree that might have been skipped. That would be a form of tearing. ...

Unhide Suspense trees without entanglement When a Suspense boundary is in its fallback state, you cannot switch back to the main content without also finishing any updates inside the tree that might have been skipped. That would be a form of tearing. ...

Unhide Suspense trees without entanglement When a Suspense boundary is in its fallback state, you cannot switch back to the main content without also finishing any updates inside the tree that might have been skipped. That would be a form of tearing. ...

Move hide/unhide logic to Offscreen component The Offscreen component is not a public type, yet, but once it is, it will share the same hide/unhide logic as Suspense children.

Move hide/unhide logic to Offscreen component The Offscreen component is not a public type, yet, but once it is, it will share the same hide/unhide logic as Suspense children.

Move hide/unhide logic to Offscreen component The Offscreen component is not a public type, yet, but once it is, it will share the same hide/unhide logic as Suspense children.

Wrap primary tree in Offscreen fiber type Still just acts like a fragment. Next step is to move the hide/unhide logic to the Offscreen implementation.

Add Offscreen component type Doesn't do anything special in this initial commit. Just acts like a fragment.

Always wrap Suspense children in fragment Changes the internal fiber structure of the Suspense component. When a Suspense boundary can't finish rendering and switches to a fallback, we wrap the "primary" tree in a Fragment fiber and hide all its DOM ...

Always wrap Suspense children in fragment Changes the internal fiber structure of the Suspense component. When a Suspense boundary can't finish rendering and switches to a fallback, we wrap the "primary" tree in a Fragment fiber and hide all its DOM ...

Always wrap Suspense children in fragment

Always wrap Suspense children in fragment

Always wrap Suspense children in fragment

Make ExpirationTime an opaque type ExpirationTime is currently just an alias for the `number` type, for a few reasons. One is that it predates Flow's opaque type feature. Another is that making it opaque means we have to move all our comparisons and n...

[EXTREMELY WIP] Initial lanes implementation

Make ExpirationTime an opaque type ExpirationTime is currently just an alias for the `number` type, for a few reasons. One is that it predates Flow's opaque type feature. Another is that making it opaque means we have to move all our comparisons and n...

Make ExpirationTime an opaque type ExpirationTime is currently just an alias for the `number` type, for a few reasons. One is that it predates Flow's opaque type feature. Another is that making it opaque means we have to move all our comparisons and n...

Make ExpirationTime an opaque type ExpirationTime is currently just an alias for the `number` type, for a few reasons. One is that it predates Flow's opaque type feature. Another is that making it opaque means we have to move all our comparisons and n...

[WIP] Convert from constructors back to constants

Make ExpirationTime an opaque type ExpirationTime is currently just an alias for the `number` type right now, for a few reasons. One is that it predates Flow's opaque type feature. Another is that making it opaque means we have to move all our compari...

Fork Dependencies and PendingInteractionMap types These contain expiration times

Stop using ExpirationTime to represent timestamps Follow up to the previous commit. This converts the remaining places where we were using the ExpirationTime type to represent a timestamp, like Suspense timeouts.

Remove expiration times train model In the old reconciler, expiration times are computed by applying an offset to the current system time. This has the effect of increasing the priority of updates as time progresses. Because we also use expiration tim...

Add LanePriority type React's internal scheduler has more priority levels than the external Scheduler package. Let's use React as the source of truth for tracking the priority of updates so we have more control. We'll still fall back to Scheduler in t...

[WIP] Convert from constructors back to constants

[WIP] Convert from constructors back to constants

[WIP] Convert from constructors back to constants

[WIP] Convert from constructors back to constants

Make ExpirationTime an opaque type ExpirationTime is currently just an alias for the `number` type right now, for a few reasons. One is that it predates Flow's opaque type feature. Another is that making it opaque means we have to move all our compari...

Make ExpirationTime an opaque type ExpirationTime is currently just an alias for the `number` type right now, for a few reasons. One is that it predates Flow's opaque type feature. Another is that making it opaque means we have to move all our compari...

Fork Dependencies and PendingInteractionMap types These contain expiration times

Remove expiration times train model In the old reconciler, expiration times are computed by applying an offset to the current system time. This has the effect of increasing the priority of updates as time progresses. Because we also use expiration tim...

Fork Dependencies and PendingInteractionMap types These contain expiration times

Remove expiration times train model In the old reconciler, expiration times are computed by applying an offset to the current system time. This has the effect of increasing the priority of updates as time progresses. Because we also use expiration tim...

Fork Dependencies and PendingInteractionMap types These contain expiration times

Fork Dependencies and PendingInteractionMap types These contain expiration times

Fork Dependencies type Contains an expiration times

[WIP] Make expirationTime an opaque type Need to replace all > and < comparisions with utility functions.

[WIP] Make expirationTime an opaque type Need to replace all > and < comparisions with utility functions.

Stop using ExpirationTime to represent timestamps Follow up to the previous commit. This converts the remaining places where we were using the ExpirationTime type to represent a timestamp, like Suspense timeouts.

Remove expiration times train model In the old reconciler, expiration times are computed by applying an offset to the current system time. This has the effect of increasing the priority of updates as time progresses. Because we also use expiration tim...

Add LanePriority type React's internal scheduler has more priority levels than the external Scheduler package. Let's use React as the source of truth for tracking the priority of updates so we have more control. We'll still fall back to Scheduler in t...

Add LanePriority type React's internal scheduler has more priority levels than the external Scheduler package. Let's use React as the source of truth for tracking the priority of updates so we have more control. We'll still fall back to Scheduler in t...

Stop using ExpirationTime to represent timestamps Follow up to the previous commit. This converts the remaining places where we were using the ExpirationTime type to represent a timestamp, like Suspense timeouts.

Remove expiration times train model In the old reconciler, expiration times are computed by applying an offset to the current system time. This has the effect of increasing the priority of updates as time progresses. Because we also use expiration tim...

Remove expiration times train model In the old reconciler, expiration times are computed by applying an offset to the current system time. This has the effect of increasing the priority of updates as time progresses. Because we also use expiration tim...

Add LanePriority type React's internal scheduler has more priority levels than the external Scheduler package. Let's use React as the source of truth for tracking the priority of updates so we have more control. We'll still fall back to Scheduler in t...

Add Lane type React's internal scheduler has more priority levels than the external Scheduler package. Let's use React as the source of truth for tracking the priority of updates so we have more control. We'll still fall back to Scheduler in the defau...