Pkg3: defaults of open vs closed about juleps HOT 3 CLOSED

I guess the only time you really need strict mode to make sure you haven't used something that you didn't save in the current environment is when you're running tests, so as long as tests run in strict mode, it should be ok.

from juleps.

Something that can be uniformly opted into (when desired) in either interactive mode or script mode, probably with the same default for both. It's not a very satisfying answer, but command-line flag and/or language-level API - global or scoped constructs for changing permissiveness mode? Making code loading differ between REPL and scripts by default would be a departure.

There is value to having both permissive and strict modes for code loading, but making strict the default would mean you need solid tooling to get much done. Pkg3 environments will provide that tooling, but seem like a feature that you shouldn't need to think too hard about until you're really deploying Julia code. I think that could make for more of a hurdle than the current transition from REPL code to script.

I see people write single-file modules and do push!(LOAD_PATH, pwd()) pretty often, and I don't think they'll want to worry about modifying a toml file to get that to work when run in a script.

from juleps.

I had thought about making include locked down too. What criterion would make sense?

from juleps.