Skip to content

Blox deviations - #46

Draft
hcollinsblox wants to merge 3 commits into
mainfrom
blox-deviations
Draft

Blox deviations#46
hcollinsblox wants to merge 3 commits into
mainfrom
blox-deviations

Conversation

@hcollinsblox

Copy link
Copy Markdown

No description provided.

hcollinsblox and others added 2 commits August 6, 2026 15:00
Work run during a drain can call `schedule`, which appends to the table the
drain is walking. Generalised iteration is not guaranteed to reach entries
added after it started, so an effect scheduled by another effect could be
skipped for the rest of the batch and then discarded by the `table.clear`
that ends it.

Both drains now index by position, which re-reads the length each time round.

Co-authored-by: Cursor <cursoragent@cursor.com>
Blox has been running a copy of this file with seven additions on top. They are
brought back here so there is one implementation rather than two, each marked
BLOX with the reason it exists so they can be reviewed separately:

  1. `peek`, which reads without subscribing and passes a plain value through
  2. `isGetter` / `isCallable`
  3. an optional `scheduleWork` per effect, which also defers the first run
  4. a cleanup function returned from an effect body
  5. `debugName` on signals, computeds and effects, plus an internals flag
  6. `createInternalSource`, which notifies without flushing
  7. reporting for a read that named no scope, which subscribes nothing and so
     reads correctly once and then never updates

Diagnostics arrive through `setHooks` and `configure` rather than a dependency,
so nothing here knows about the runtime using it. Blox's copy read them from its
own Debug and Profiler modules, which is what kept the file from living here.

Co-authored-by: Cursor <cursoragent@cursor.com>
@jkelaty-rbx

jkelaty-rbx commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

Can you instead submit this in the form of 1 or more feature requests (github issues or individual PRs)? This seems to be a collection of ad-hoc changes that are all somewhat related, but not quite.

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.

2 participants