In Julia, a lot of the Base and closer related functions are also written in pure Julia, and the code is easily avaible. One can skim through the repository or the local dow
Though this may not be what the OP is looking for, @less
is very convenient to read the underlying code (so I very often use it). For example,
julia> @less 1 + 2
gives
+(x::Int, y::Int) = box(Int,add_int(unbox(Int,x),unbox(Int,y)))
which corresponds to the line given by
julia> @which 1 + 2
+(x::Int64, y::Int64) at int.jl:8
This is not currently supported but probably will be in the future.
@edit functioninquestion()
will open up your editor to the location of the method given.
It probably wouldn't be to hard to take the same information used by @edit
and use it to open the file and skip to the method definition, and then display it directly in the REPL (or Jupyter).
EDIT: While I was answering, somebody else mentioned @less
, which seems to do exactly what you want already.
There is now another tool for this, https://github.com/timholy/CodeTracking.jl. It is part of Revise.jl (and works better when also using Revise). It should work inside Jupyter and with functions defined in the REPL, unlike @edit/@less.