18
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Jan 2026
18 points (95.0% liked)
TechTakes
2416 readers
169 users here now
Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.
This is not debate club. Unless it’s amusing debate.
For actually-good tech, you want our NotAwfulTech community
founded 2 years ago
MODERATORS
Doesn't look interesting to me. NB I'm not a Swifty. If you're someone looking to make a compile-time dependency injection validation framework, cycle detection seems like an early feature to add, and feels like a pretty early unit test to implement.
E: read response from BurgersMcSlopshot please :)
DI frameworks are tricky beasts. Either they sacrifice flexibility for simplicity (I've seen this done in Go and in Scala, where the DI essentially generates basic instantiation and more advanced resolution is left to the app developer) or they can get really complex but do some handy things (.Net 4.x DI frameworks like Castle Windsor provided some neat lifecycle management tools but was internally very complex).
Cycle detection gets a little hairer the more complex a dependency/ class of dependencies gets. The process itself doesn't change but the internal representation of the graph needs to be sufficiently abstract enough to illustrate a cycle for all possible resolution scenarios.
Based on the commit to fix the particular bug, it looks like the change will address a specific scenario but will probably fail to address similar issues.
All this to say "the problem isn't too hard to think about but the solution isn't straight-forward", also "this is a fine short- term fix but longer-term would involve redefining the internal representation of a dependency graph", and finally " An LLM-provided solution is at best a band-aid, in the most generous light.'
Thanks so much! Now I can waste my life on more interesting things...
I see. I guess I was thinking too abstractly about how a system like this might work.