Kristoffer Carlsson
Kristoffer Carlsson
> I think it would be reasonable for Julia to persistently store only depot-relative (or potentially loaded-package-relative) paths and reconstruct them on demand. We do this for the list of...
If this works well for you then it's fine by me.
I am personally not a big fan of: - More environment variables to control small details of default behavior - Surprising interactive input from commands that are not always interactive.
> The interactive ask is gated behind isinteractive(), so this shouldn't happen. My point is that `add` typically does not have interactive behavior so I often run it, tab away,...
I'd say that having interactive input deep inside functions like this is non-workable because you don't know what contexts they are called in.
I'm going to close this since the released `workspace` feature is the official way of sharing a manifest. The `manifest = ` was always a bit of a hack and...
Is this documented? I thought the env var was the "official way" (although the kwarg is better).
> Do you have a quick measurement for the overhead? Doing some updates now, will measure afterwards. I'm pretty sure the current Tracy.jl implementation does not allocate though. Will check...
Ok, I have three implementations now: 1. A single global `RefValue` which we set the current block and then reset it, useful for bootstrapping, perhaps when we don't have much...
I think this would be good to have to restore some functionality we mused to have and allow for future customizations of the zones from julia. I'm happy for a...