Sebastian Pfitzner

Nope. Seems like something *really* breaks (or maybe there's just too much being printed?).

A callback that's called every once in a while (i.e. every x instructions) seems like a good solution, imho.

The Cassette-less alternative to this (at least for file breakpoints) would be some kind of Infiltrator/Debugger hybrid. Setting a breakpoint in whatever UI would recompile the relevant method with an...

We could temporarily pop them from `compiled_methods` when someone tries to set a breakpoint in one of them. I think it does make sense to these kinds of methods by...

You mean for something like ``` julia> f(x; y=3) = x+y f (generic function with 1 method) julia> @breakpoint f(2, y=3) breakpoint((::getfield(Main, Symbol("#kw##f")))(::Any, ::typeof(f), x) in Main, line 0) julia>...

More generally, could we add a callback function to breakpoints? I'm not sure what one could want to do with it, but it sounds like a cool idea imho :)

You can always use `Docs.doc` or similar directly, so maybe that's convenient enough? ``` julia> @enter gcd(2,3) In gcd(a, b) at intfuncs.jl:49 49 function gcd(a::T, b::T) where T50 a ==...

What's probably tripping you up here is that we're not automatically stepping through the kwarg wrapper for `open` here (see [here](https://gist.github.com/pfitzseb/cd09671e4b0d1f2557f8e4649064df44) for how you can step to the `println` call)....

Those statements are all on line 1 -- same as for the `@code_lowered` output: ``` julia> code_lowered(open, (Function,)) 1-element Array{Core.CodeInfo,1}: CodeInfo( 1 ─ %1 = (Core.NamedTuple)() │ %2 = (Base.pairs)(%1)...

We should maybe make it more clear that we only ever care about calls, never about assignments etc.