Jeff Bezanson

how should variables in interactive expressions work?

1

If we support arbitrary expressions at the julia prompt within the debugger, then they can have their own local variables, including compiler-inserted temporary vars. Currently expressions share an environment with...

Not a high priority at all, but I noticed this: ``` julia> using ASTInterpreter WARNING: module Lexer should explicitly import √ from Base julia> eval(ASTInterpreter, :(fancy_mode = true)) true julia>...

use normal expression printer when we don't have source code

2

The terminal graphic tree display is really cool but it's too verbose for most purposes. We should just show the expressions the way julia usually does. Example: ``` julia> f()...

This is an approach to #30 that I feel would be best, as it follows standards that are pretty well established at this point. - `[]` are the same as...

Currently the libsupport code needed is checked in. It should be pulled from the libsupport repo at build time.

Currently values can be used as type parameters if they are isbits, or tuples of bits and symbols. That is a bit arbitrary, and it seems to me we might...

support foreign threads, and adding threads at run time

5

Hook a couple functions (notably cfunction and jl_call*) to handle adding foreign threads automatically. Fixes #17573

serialize bits values and QuoteNodes in IR encoding

2

Using this instead of the `roots` array avoids scaling problems in functions with many constants. This might also be better for precompiling. Grows the system image by 1.6%, but is...

Types in method signatures are shown as e.g. `x::Core.Any`, which gets very verbose. `Core` can always be omitted if the name is exported. `::Any` could be omitted as well.

The docs for this package are great, but I was surprised to see that `?optimize` doesn't turn up anything. Would be nice to add doc strings.