Juno 0.8 is out – get it while it’s fresh!
While there of course have been loads of small bugfixes, the three stand-out features of this release are:
Juno now provides a fairly complete debugging experience, thanks to all the recent work on JuliaInterpreter.jl. Also see the recent blog post.
The API to access the debugger consists of
Juno.@runto run an expression and stop at any breakpoints, and
Juno.@enterto step into the function and start stepping on the first line.
There are UI elements for setting breakpoints
- in files, by clicking the empty space left of the line numbers, or
- when entering a function/method , by using the
Break on...text box on the right – either enter a function name (e.g.
sin) to set breakpoints for all methods of that function, or specify the argument types (e.g.
These breakpoints are unconditional by default, but can be switched to conditional breakpints with the button on the right.
Important: If you want to set breakpoints in files you need to have loaded Revise.jl and Revise needs to be aware of the file in question. This means that you can only set breakpoints in your own scripts (that are not part of a package) if you have
This has been in Juno for a while now, but mostly hidden. Use
Juno.@traceto get inline performance annotations for your functions, provided by Traceur.jl.
Important : Restart Atom before updating
ink and do not start a Julia session.
If that does not work, close all Atom instances and type
apm uninstall ink apm install ink apm uninstall julia-client apm install julia-client
into a terminal.
As always, make sure all Julia and Atom packages are up-to-date.