Traceur.jl icon indicating copy to clipboard operation
Traceur.jl copied to clipboard

Results 13 Traceur.jl issues
Sort by recently updated
recently updated
newest added

As [suggested](https://github.com/JunoLab/Traceur.jl/issues/47#issuecomment-810772809) by @c42f, wrap the trace call in `with_logger()`. While we are at it, instead of the global logger, would [current_logger()](https://docs.julialang.org/en/v1/stdlib/Logging/#Logging.current_logger) be worth considering ?

I do not understand the following warnings, the variable names seems to be left out and is it really a problem if something is assigned as `Nothing` or a `Tuple`?...

bug

I'd like to see stack traces for each warning. Often, I have warnings in Julia-owned files like `math.jl` or `operators.jl`. I'd like to be able to see, where in my...

enhancement

I think a (probably opt-in only) warning for generated `@boundscheck` statements would be very helpful. Sometimes, there is code with multiple (inline) functions and nested control flow. In those cases,...

enhancement

The below code works fine on Julia 1.5, but gives an error on the latest Julia master. Code: Click to expand ```julia julia> import InteractiveUtils julia> InteractiveUtils.versioninfo(; verbose = true)...

bug

## Summary Traceur + Zygote + nested differentiation = :( ## Minimum working example I've tested this on Julia `1.2.0-rc2.0` and `1.3.0-alpha.0`. Julia 1.2: ```julia julia> using InteractiveUtils, Pkg julia>...

Traceur is substantially more useful for me when I use the `modules` keyword from #24 , otherwise I'm flooded with warnings from Base and other modules I didn't develop. For...

For some reason my program seem to be stuck at the very beginning (reading in a corpus, before training can be performed on that corpus) when I prepend the `train`...

If one defines a method, uses `@trace` on that method and then redefines the method and runs `@trace` on it again, it will give the output from the *old* method...

bug

Traceur appears to install correctly, and I see no error messages either when `using` or when invoking the `@trace` macro, but I also see no trace output, just the returned...