Sebastian Pfitzner

This is gonna be slightly annoying to implement. In the meantime I'd recommend `@doc`: ``` julia> foo(x) = @infiltrate foo (generic function with 1 method) julia> foo(3) Infiltrating foo(x::Int64) at...

That's because it's not specific to Infiltrator at all (the same works in the normal REPL). But yes, adding a note can't hurt: https://github.com/JuliaDebug/Infiltrator.jl/commit/bc6fbcfd36f1f68a2bdccf24c3f0f6e9bb0ec9f6

I see an additional error in Juno: ``` Uncaught TypeError: Cannot read property 'legend' of undefined ``` which is thrown from inside the webview that contains the plot. Not sure...

> To start with, toplevel/module scope is probably fine and we could throw something together quickly for that, I think. Agreed. I also think that it's not hugely important for...

This is only relevant when the higher order function the functor is passed to has a strict type constraints on `Function` (instead of e.g. `Base.Callable`).

Note that the macro case is something we can't really support in full generality since macros are allowed to to _everything_.

Re the callable types point: I just tried that locally on master with a minimal definition and didn't see any lint errors, so that case seems fixed.

Let's leave this open for now, I think. We can improve our docs in the short term and the behaviour in the long term.

Same. The current situation (CSTParser being used, JuliaSyntax not so much) is a bit annoying, but the solution to that is to kill off CSTParser too :)

On it. AFAIK this *should* only happen when Julia is started with `--color=yes`, so there shouldn't be any problems with Juno release.