73
Introducing Predictive Debugging: A Game-Changing Look into the Future
(blog.jetbrains.com)
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 01 Aug 2023
73 points (100.0% liked)
Programming
17385 readers
309 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 1 year ago
MODERATORS
They do say that, but how much can it be trusted? Can they really detect all native interface calls? Be aware of all future file system checks or event driven programming paradigms?
hashset.getOrElse()where uniqueness decides future flow? I'm sure we will be experiencing or at least seeing bug reports related to predictive debugger triggering mutations.I'm struggling to see how bug reports found using this prediction approach would ever be sent as anything but bugs of the predictive debugger itself.
how would end-users ever see bugs caused by a debugger the devs use? how would users of a third-party library conflate bugs in their own code/the third-party code when you can see which lines are which as you debug?