Skip to content

Exec-next: improve null propagation errors#5644

Merged
rmosolgo merged 8 commits into
masterfrom
exec-next-null-propagation
Jun 23, 2026
Merged

Exec-next: improve null propagation errors#5644
rmosolgo merged 8 commits into
masterfrom
exec-next-null-propagation

Conversation

@rmosolgo

@rmosolgo rmosolgo commented May 26, 2026

Copy link
Copy Markdown
Owner

Null propagation basically works, but the errors produced aren't quite right yet.

Fixes #5622

TODO:

  • Implement top-level eager killing I removed it -- the existing support worked well enough.
  • Further unify finalizers and error results? These are almost the exact same structure.
  • Look at where finalizers and error results are merged. I think they clobber each other in some cases.

@rmosolgo rmosolgo added this to the 2.6.4 milestone May 26, 2026
@rmosolgo rmosolgo modified the milestones: 2.6.4, 2.6.5 Jun 22, 2026
@rmosolgo rmosolgo merged commit c9b40a7 into master Jun 23, 2026
12 of 13 checks passed
@rmosolgo rmosolgo deleted the exec-next-null-propagation branch June 23, 2026 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Exec-next: halt when a non-null error is encountered

1 participant