Kristoffer Carlsson
Kristoffer Carlsson
With the stdlibs now running, it seems the REPL tests deadlock. Perhaps this is something to do with the tasks in the REPL tests (which are notorious for deadlocking if...
FWIW: Here is the result with running all stdlibs (except REPL) Julia Version 1.2.0-DEV.321 Commit a03da7312e* (2019-02-14 05:43 UTC) Platform Info: OS: Windows (x86_64-w64-mingw32) CPU: Intel(R) Core(TM) i9-9900K CPU @...
I took the liberty of updating the table with the latest stdlib run on master.
I wonder if the file should just be automatically generated if it doesn't exist during precompilation time instead of having this as a build step. If you add the package...
You can just hoist the part computing the output expression into a function and debug that one.
I don't get what you mean. ``` macro foo(expr) _foo(expr) end function _foo(expr) ... end ``` and debug `_foo`
It doesn't really make sense to me to debug the macro expansion during runtime because that is not when it is executed.
> Here I didn't mean the macro expansion, but the code it generates. Oh, I got confused because that already works.
`n` will take you to the next call. Introducing new local variables is not supported, you can do `global asdf =... `
Well, not really the next call but the next call that is on a line greater than the current line.