![]() ![]() The new functionality is available inside the Debugger tool window (click the Trace Current Stream Chain button). The Java Stream Debugger plugin, which visualizes Java Stream operations, is built into IntelliJ IDEA 2017.3. The Instrumenting agent option is enabled by default.įor this code example, we’ll have the following stack trace: The new Instrumenting agent causes very low overhead. IntelliJ IDEA 2017.3 extends the Async Stacktraces feature with a new Instrumenting agent, which provides almost the same functionality and works out of the box as common capture points are built-in. The Async Stacktraces feature shows the combined stack traces of all threads. In addition, a renderer can be “muted” from the context menu. To enable On-demand Data Renderers for each renderer, go to the Data Renderers settings page. Simply click on them when needed, instead of having them evaluated automatically: Now, the evaluation of the values in Variables, Watches, and other places can be done on demand. One more enhancement to the debugger is the new On-demand Data Renderers feature that helps reduce overhead. It displays the overhead added either when stepping over the code or when Data Renderers evaluate values. There’s a new Overhead tab in the Debugger tool window. Smart Completion in IntelliJ IDEA 2017.3 is aware of type casts and uses them to suggest chains of method calls. Open the Settings/Preferences dialog select Editor | Inspections, and click on the Filter icon. Note that there’s an easy way to find all the new inspections. There’s a new intention action called Unroll loop: You will also find new inspections for the Fuse Stream API call chain: ![]() The IDE now detects duplicating Map keys and duplicating Set elements. The inspection for Inverting a boolean method is now available on-the-fly. Redundant throws declarations can now be detected and fixed on the fly.įor deprecated code, the IDE now suggests a quick-fix if there is a replacement method in the JavaDoc. It offers a quick-fix to explicitly declare the inferred annotation: The updated inspection infers nullability annotations for parameters of sealed and private methods: It now even detects issues that were not obvious: We’ve made the data flow analysis for the Optional type even smarter: You can replace code that iterates to find a maximum or a minimum with Stream.max and Stream.min: Now you can replace StringBuilder usages with llect and Collectors.joining: The IDE now detects possible nullability issues in Stream API call chains: IntelliJ IDEA 2017.3 has loads of new improvements made to the data flow analysis. In this post, we’d like to give you a glimpse of the highlights of the upcoming release. We are constantly working to improve user experience and productivity, and, of course, on bug fixes. We are committed to creating a better product, we really appreciate your input when you share your feedback and send us bug reports. IntelliJ IDEA 2017.3 is now available for public preview! Everyone is welcome to download the public preview build right away.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |