You can import stuff from “above” with ..Thing, such as: module Mod # Define some common types. struct T1; field::Int64; end struct T2; field::Float64; end # Define a sub module. Maybe this would even live in a different file. It assumes that # T1 and T2 are available in its parent, but it doesn'…

I get the consistency argument, but I’m not sure I understand this one: [image] tuckermcclure: The problem with this final line is that it requires Sub to know who its parent is ( Mod1 ). If Sub is intended to be used by a lot of different utilities, then it naturally can’t know who its parent …

Hi @ffevotte . Good question. Here’s a simple example that captures the essence of a real problem we’re having at my company: Suppose we have a MyTypes module that exports a bunch of common types. Those types are on the interface for functions in the Subsystem module. Now we want to build two separat…

[image] tuckermcclure: That’s all just context to answer your question, François. This thread should still be about whether or not ..: is useful and should be prioritized. Well, I’m sorry to derail this further but, on the other hand, I feel like this proposal is more likely to be prioritized…

Wow, @ffevotte , thank you for that amazingly detailed reply! Let me clarify two things: SystemA and SystemB are intended to be totally separate programs. I understand that the two instantiations of MyTypes are different there. That’s intended. The two systems just happen to be next to each other…

Here’s a link to the new post about first-class support for local, unregistered packages. [image] Could we make first-class support for packages that are "just files" and not repositories? General Usage I keep circling around the same issue from a variety of different van…

[image] tuckermcclure: I would like to use packages. […] BUT! I need everything in the same repo. Feature request: Store multiple registered packages in a single Git repository opened 04:36AM - 14 Jul 19 UTC (UTC) …

That’s cool. Thanks @Tamas_Papp . Still a work in progress, I see, but it’s good to know about. I’ll have to think about how this would possibly work in the context of private repos. E.g., our sim’s going to run in Docker without Git credentials, so it won’t be able to hit our private repo, but as l…

Import types "above" a module with ..: for consistency and brevity?

General Usage

tuckermcclure April 3, 2020, 1:00am 6

Here’s a link to the new post about first-class support for local, unregistered packages.

Topic		Replies	Views
Problems with signature changes of imported local modules on include General Usage module	26	937	October 19, 2023
Proper way of organizing code into subpackages New to Julia packages , code-organization	48	8369	August 24, 2022
Organization of multiple modules in same package General Usage packages , modules , code-organization	18	5485	May 4, 2021
Possibility of `local import` statements in future? Internals & Design scope	63	4108	May 2, 2018
Dependencies of src files inside a package General Usage dependencies	10	2709	July 17, 2020

Import types "above" a module with ..: for consistency and brevity?

Related topics