Skip to content

Simplify setImmediate polyfill handling in EM_TIMING_SETIMMEDIATE#26984

Merged
sbc100 merged 1 commit into
emscripten-core:mainfrom
sbc100:EM_TIMING_SETIMMEDIATE
May 20, 2026
Merged

Simplify setImmediate polyfill handling in EM_TIMING_SETIMMEDIATE#26984
sbc100 merged 1 commit into
emscripten-core:mainfrom
sbc100:EM_TIMING_SETIMMEDIATE

Conversation

@sbc100
Copy link
Copy Markdown
Collaborator

@sbc100 sbc100 commented May 20, 2026

Some of this logic seems to be from the --proxy-to-worker days, and that settings was removed a while back.

@sbc100 sbc100 force-pushed the EM_TIMING_SETIMMEDIATE branch from 4f9f408 to 73c1b95 Compare May 20, 2026 21:11
@sbc100 sbc100 requested review from dschuff and kripken May 20, 2026 21:13
Comment thread test/test_emscripten_main_loop_setimmediate.c
@sbc100 sbc100 force-pushed the EM_TIMING_SETIMMEDIATE branch from 73c1b95 to 2028d1d Compare May 20, 2026 21:33
@sbc100 sbc100 changed the title Simplify setImmediate polyfill handling in EM_TIMING_SETIMMEDIATE Simplify setImmediate polyfill handling in EM_TIMING_SETIMMEDIATE May 20, 2026
@sbc100 sbc100 merged commit f573345 into emscripten-core:main May 20, 2026
30 checks passed
@sbc100 sbc100 deleted the EM_TIMING_SETIMMEDIATE branch May 20, 2026 22:29
sbc100 added a commit to sbc100/emscripten that referenced this pull request May 22, 2026
In emscripten-core#26984, I changed the format of this message so it no longer includes
the `target` key.

I should have also remove this extra handler here, which is actually
doing nothing.  There is no need to explicitly do any kind `no-op`
handling since all messages that don't have a `cmd` key are already
completely ignored by this handler.
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