Shuhei Kadowaki
Shuhei Kadowaki
Are you proposing an optimization where the optimizer replaces `string(...)::String` with `lazystring(...)::LazyString` when the return value is passed into an `
I thought we could just restrict the scope of `unoptimize_throw_blocks` to the `string(...)` calls that are known to be `throw`n.
Setting your own keybinds to select autocompletions isn't enough for you ? I really don't think selecting completions on each space hitting is what everyone wants.
now the command is not defined for the julia scope, since you only need to use that for the weave scope.
> That said, I'm not sure if we need to be so strict here yep, the only reason I made those changes was not to allow users to dispatch the...
I'm actually very in favour of @pfitzseb . I'm just an inexperienced Julia programmer, but feel like we beginners want to first refer to the outermost call and then continue...
I'm going to deprecate this package from the next JET.jl minor release. For now, please checkout to the latest master of JET.jl and use `@report_opt`: https://aviatesk.github.io/JET.jl/dev/optanalysis/ That should work on...
> What happens if you change and re-eval a function (or even the currently debugged function)? Does the debugger pick up on that? If you evaluate the other function (i.e....
So the idea is to accomplish something similar to what we can do with LocalPreferences.toml and the `skip_precompile` setting, but automatically? Or is something more advanced wanted here?
> Will this need to be backported to 1.9 since it's a bugfix to the effect system? Yes, I think we should do it.