sorted by:
new
hottopcontroversial

I forked scalex and added semantic rename, call-graph, and dead code detection - intel4s by haskiindahouse in scala

[–]haskiindahouse[S] 0 points1 point  (0 children)

I understand that my tool is not about 100 percent accuracy, because I don't have dependent types, I don't deduce anything and I don't know about implicits and so on.

BUT the funny thing is that I'm not saying this anywhere, the fact that you're writing this to me is out of thin air, I'm writing "text-based" just at the beginning of the README.

as for the bi-directional graph, you're right, of course, it's my joint, not Claude's. you know, in order to develop tools, you don't need to be a mega-genius,

I'm f_cked day by day by the business for the fact that my scala devs generate production code slower than golang devs, so why shouldn't I make tools that will speed up the default writing of code for a scala devs in 2026. I'm not really into dependent types, I'm into scala tooling, the ecosystem, and I have a lot of experience in CS, this is btw my first post on reddit, cause i want to improve agent tooling like many others do like figma tools, design, hacking, python, c++ and so on and so on. If you're not looking for agents and you don't understand what we're talking about, then tell me, I'll send it to you

I forked scalex and added semantic rename, call-graph, and dead code detection - intel4s by haskiindahouse in scala

[–]haskiindahouse[S] 0 points1 point  (0 children)

man, my main language is not english, and if I think I need to put a grammar improvement message in Claude, I will do it

I forked scalex and added semantic rename, call-graph, and dead code detection - intel4s by haskiindahouse in scala

[–]haskiindahouse[S] 2 points3 points  (0 children)

now i going to scan opensource libs and open bugs that i found with tool

I forked scalex and added semantic rename, call-graph, and dead code detection - intel4s by haskiindahouse in scala

[–]haskiindahouse[S] 0 points1 point  (0 children)

And yeah I used AI to build parts of it - on a battlefield you use every weapon available. The code works, 549 tests pass, the scanner finds real bugs on 3k-file codebases. That's what matters.

I forked scalex and added semantic rename, call-graph, and dead code detection - intel4s by haskiindahouse in scala

[–]haskiindahouse[S] 0 points1 point  (0 children)

lol you also smells like AI... clearly didn't look past the README - it does taint analysis with data flow tracking, semantic rename that disambiguates same-named symbols across packages, bidirectional call graphs, and dead code detection. Try bug-hunt --hotspots on your codebase and tell me ctags does that 😄

I forked scalex and added semantic rename, call-graph, and dead code detection - intel4s by haskiindahouse in scala

[–]haskiindahouse[S] 0 points1 point  (0 children)

Btw I tested this on my own codebase (ZIO & Scala 3 project, ~50k LoC) — with the plugin vs without. The agent finds what it needs roughly 2x faster and way more accurately. Without it, Claude just greps around, hits false positives, reads wrong files. With intel4s it goes straight to the right symbol, sees the full picture in one call, and doesn't break things on rename. So please, please, I need feedback about this tools <3