How Unhandled Exception Works
summary
PhpStorm adds an unhandled-exception inspection that stores heavy analysis results as persistent on-disk signatures so control-flow and throw information aren’t reparsed for every file open. The engine caches per-function results, avoids full reindexing when possible, performs up to three-level deep analysis, and provides a surround-with-try/catch generator; conservative invalidation keeps correctness. Measured improvement: reopen latency is reduced (about 1.5× faster in version 18.1), lowering CPU work while shipping the feature.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:31Exception handling tasks
- 3:21Exception checks evolution
- 7:50Caching invalidation issues
- 14:22Static analysis optimization
- 23:01Exception types config
- 26:34Exception inspections
- 27:40Writing clear code
- 29:08Anonymous stats feedback
- 31:23AI stats Q&A
- 33:43JetBrains workflow
- 36:59Code search navigation
- 38:28Company goals
related talks
39mWhat's coming in PhpStorm
27mDebugging with Debug and PhpStorm
38mLeveraging Typed Exceptions for Cleaner Error Handling
51mExceptions in PHP: more complicated than it appears
51mLeveraging Typed Exceptions for Cleaner Error Handling
42mLeveraging Typed Exceptions for Cleaner Error Handling
22mWhat's New in Xdebug?
32mFrom Zero to Static Analysis Hero