Skip to content

Conversation

PLPeeters
Copy link

@PLPeeters PLPeeters commented Aug 29, 2025

Fixes #20, #35

@sbc100
Copy link

sbc100 commented Sep 23, 2025

Can this PR be landed? It seems like it would make the tool much more useful.

@albertas
Copy link
Owner

Can this PR be landed? It seems like it would make the tool much more useful.

Sure, I am going to create new release this week. It will include this fix.

sbc100 added a commit to emscripten-core/emscripten that referenced this pull request Sep 24, 2025
There are still quite a few false positives after this but they are fall
into basically 2 classes:

- Subclasses of TestCase, which are explicitly used
- Subclasses of Library, which are no explicitly user
- Settings, which are only ever read in the JS compiler.

I think we should probably wait until the `deadcode` tool at least
supports returning error codes before we try to integrate into CI. See
albertas/deadcode#36
@PLPeeters
Copy link
Author

@albertas Don't want to be pushy, but I'm eagerly awaiting a release on this :)

@sbc100
Copy link

sbc100 commented Oct 2, 2025

@albertas Don't want to be pushy, but I'm eagerly awaiting a release on this :)

We ended up use vulture for now since it does return and error code already: emscripten-core/emscripten#25382. I'm not sure what the differences are, but they seem pretty similar.

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.

[bug] Command's exit code is 0 when dead code is found

3 participants