72
Introducing Predictive Debugging: A Game-Changing Look into the Future (blog.jetbrains.com)
submitted 3 years ago by to c/programming@programming.dev
22 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 3 years ago (1 child)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 years ago

    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?

  • permalink
  • fedilink
  • source
  • parent