this post was submitted on 12 Aug 2026
59 points (98.4% liked)

Programming

28256 readers
222 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
59
Periphery as open source project is ended. (periphery.pro)
submitted 2 weeks ago by pylapp@programming.dev to c/programming@programming.dev
16 comments fedilink hide all child comments
 

Periphery, a famous and efficient tool to check dead code, moves from open source model to commercial model 😭

you are viewing a single comment's thread
view the rest of the comments
[–] eleijeep@piefed.social 2 points 2 weeks ago (1 children)

Was it really useful? Code coverage tools have existed for forever. Does Swift not have any FLOSS coverage tools like gcov?

[–] urushitan@kakera.kintsugi.moe 3 points 2 weeks ago (1 children)

Code coverage tools are generally specifically about test coverage, not which code actually gets executed or is unreachable. It makes sense in swift because code with tests would still report as being covered even if the actual UI that would ever run that code was removed. That’s what this tool looks for. Dead code, not untested code

[–] eleijeep@piefed.social -1 points 2 weeks ago

I know what the tool does, I read the webpage.

Code coverage tools are generally specifically about test coverage, not which code actually gets executed or is unreachable.

Code coverage tools are for whatever you want to use them for. Lots of people use them to measure test coverage, but you can also use them to measure code usage in production. There are a variety of different ways to instrument code of various different levels of invasiveness and performance impact. Even the Linux kernel has built in instrumentation for measuring code coverage (kcov).