Developers interested in trying the new compiler can activate it using the -yjit command-line option. In it, only the beginning of a method is compiled at first, while the rest follows incrementally once the type of arguments and variables have been dynamically determined. YJIT was developed at Spotify to improve the performance of the team’s Ruby on Rails applications, through an approach called Lazy Basic Block Versioning. The feature is still experimental and limited to Unix-like x86-64 platforms, but promises a short warmup as well as speedups “from 15 to 19 per cent” over the CRuby interpreter. IRB users who want to prevent making mistakes in the first place now have an autocompletion function with documentation dialog at their disposal.Īnother interesting addition is the new in-process JIT compiler YJIT. To improve the debugging experience even further, Ruby 3.1 ships with an error_highlight gem, which is enabled by default and adds more precise error locations to backtraces. It also includes record and replay functionality, a tracing feature, and supports Visual Studio Code as well as the Chrome browser as debugging front ends. The new debug.gem is meant to put an end to those by not slowing down applications when looking for errors and sporting useful capabilities for remote and multi-thread debugging. According to Ruby committer Yui Naruse, lib/debug.rb wasn’t well maintained and showed some performance and feature issues. Version 3.1 is now available and mostly bestows performance and debugging improvements upon developers.Īmongst the highlights of version 3.1 is a new debugger that replaces lib/debug.rb. As has become the custom, the team behind Ruby has used the end-of-year holiday break to push out a feature update for the programming language.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |