Shuhei Kadowaki

Indeed, the code passed to `@btime` is internally represented as an `Expr` object, and BenchmarkTools.jl fundamentally executes this using `Core.eval`. JET doesn't analyze these `Expr` objects, becauset Julia's metaprogramming features...

Indeed. Well, alternatively, JET could consider specially analyzing expressions provided to frequently used idiom such as `@btime` as a special case. To enable this, a sort of plugin system would...

Thanks! This issue list should indeed be a handy tool for tracking possible enhancements for JET. Especially considering that these issues are often low-hanging fruit, they make great opportunities for...

It looks like the former example is because `Base.Generator` seems to lose a precise type information (see `::Base.Generator{_A, typeof(identity)} where _A` in the second line of abstract stack trace): ```julia...

> why was the `callf` indirection necessary? Ah, I just wanted to check if `@report_call` generate a reasonable type information about input function call e.g. `f::typeof(f)(args::Tuple{Vector{Vector{Int64}}}...)` (, which we can...

Should be fixed by: https://github.com/JuliaLang/julia/pull/47628

By wrapping the precompilation workload by `SnoopPrecompile.@precompile_setup`, we can turn off the precompilation via Preferences.jl. For example, you can have `LocalPreferences.toml` at the root of the project with the following...

> But you could've already done that before with the more refined precompilation controls? Yes, we can always edit the package file directly. The Preferences.jl approach is more useful when...

> That doesn't answer the question though, since it's still Preferences. I'm not sure I understand the question. SnoopPrecompile automatically loads Preferences.jl and looks for configurations specified in LocalPreferences.toml when...

Wow, it looks like SciML's documentation is even more sophisticatedly structured than I anticipated. It seems like we just need to update DiffEqDocs. I believe that this pull request is...