The infamous issue https://github.com/JuliaLang/julia/issues/28789 has been on most of our minds for a while now. Although I’ve stopped posting there, I can tell you I’ve been thinking about it a lot, as have Stefan and Jameson and others, and we have continued discussing it off and on. We should re…

[image] jeff.bezanson: Can you picture the blog post? “Julia 2.0 is here: see what’s in store!” followed by a single line of release notes saying “global scope thingy changed back”. It’s completely laughable. I would not find a blog post a la “We realized we made a mistake in a key part of ju…

Ok, I appreciate that, but it’s not happening. The number one issue is the cost/benefit analysis of having more incompatible versions of julia out there just for this one subtle scope thing. The perception stuff is secondary. Yes we may have made a mistake here, and while I’m willing to admit that I…

I wonder if the proposed solution will handle all globals the same? It shouldn’t matter whether the global is defined and used in the REPL or inside the file (module). Uniformity (and the attendant simplicity) are in my opinion much preferable to any real or imagined convenience.

[image] jeff.bezanson: The number one issue is the cost/benefit analysis of having more incompatible versions of julia out there just for this one subtle scope thing. I guess I don’t understand this point :slight_smile: Won’t there be incompatible versions out there no matter how you label th…

[image] davidanthoff: I guess I don’t understand this point :slight_smile: Won’t there be incompatible versions out there no matter how you label them? The argument applies if we’re not planning to release the change in 1.x, and also not planning to release 2.0 soon. We’d have more time with …

Let’s please keep this thread on the merits of the technical solution, not how to get there or recriminations and scolding about what has or has not been done wrong.

Just want to add a +1 to the proposed solution and deprecation path here. In fact, I would find it much more reassuring than some form of “we are following semver, but just not in this case”. Don’t get me wrong, I’m a huge proponent of SemVer - especially it’s terminology. However, the huge pra…

I, for one, thought that this change would be painful but at the end it wasn’t. Probably because I find the SoftGlobalScope solution sufficient: 1- Prototype/debug interactively and freely in IJulia, not worrying about scope 2- Do IJulia.SOFTSCOPE[] = false to catch any unintended scoping “bugs” t…

Is there a clear explanation somewhere for why the scoping rules for “children” scopes of global scope must be different for children scopes of local scopes? What edge cases exist that mean we can’t have for blocks within global scopes inherit variables from the global scope while also establishing …

Another possible solution to the global scope debacle

Internals & Design

Topic		Replies	Views
New scope solution Internals & Design proposal	233	22739	January 14, 2020
Global scope confusion again General Usage question , scope	52	7080	May 17, 2025
Local vs global scope again General Usage	30	2513	August 9, 2020
REPL and for loops (scope behavior change) General Usage	42	15380	September 16, 2020
Explain scoping confusion to a programming beginner New to Julia question	26	3371	August 11, 2020

Another possible solution to the global scope debacle

Related topics