News for hackers. Stuff that matters.
Re:LeanQt – GUI is here, Widgets are near by heavyset_go on Saturday November 12, 2022 @03:56PM (#33576985)
That feels halting problem-esque.
Re:LeanQt – GUI is here, Widgets are near by Epa095 on Saturday November 12, 2022 @05:18PM (#33577719)
It definitely is if you want a 100% correct and 100% certain answer. But if you accept 3 categories 1: this we know is used 2: this we know is not used, 3 this we don't know anything about, then it's doable.
Re:LeanQt – GUI is here, Widgets are near by colejohnson66 on Saturday November 12, 2022 @06:40PM (#33578381)
But (2) requires knowing everything the binary will do. You can’t know what something won’t do without knowing what it will do.
Re:LeanQt – GUI is here, Widgets are near by tadfisher on Saturday November 12, 2022 @07:21PM (#33578653)
You can do (2) if you can tolerate false positives. For example, if a symbol isn't referenced literally elsewhere in the binary, consider it unused, but add a configuration option to keep it in case it is referenced dynamically. The JVM world has been doing this for years with ProGuard.
Re:LeanQt – GUI is here, Widgets are near by yarg on Saturday November 12, 2022 @09:28PM (#33579344)
Branches are a problem, depending on the number of parameters needed to be evaluated:

> Solving a constraint satisfaction problem on a finite domain is an NP-complete problem in general.

https://en.wikipedia.org/wiki/Complexity_of_constraint_satis...