Now that using M: a, b does not import M per se, I found that I have to add an import explicitly when I am being very tidy with namespaces in packages (just using what I use frequently, qualify the rest). Is it possible to combine these two in a single line?

Yes, this will keep working (unless we remove the module “self reference”, which some people want, but I don’t think is likely). There was a warning in 0.7 because using M: M used to be equivalent to using M, but now will just bring in a single binding for M itself rather than everything exported fr…

Combine using M: a, b; import M

General Usage

ssfrr August 27, 2018, 8:26pm 6

Nice, I didn’t know about this. This was my only use-case for import, but now I can replace all my import M with using M: M and not need import at all.

3 Likes

Topic		Replies	Views
Trouble importing a module that depends on another globally imported module General Usage type , module	9	1975	July 19, 2019
Trouble scoping functions with module statement in v0.7 General Usage question	1	378	January 2, 2019
Relative module paths General Usage module	0	468	November 17, 2018
Import types "above" a module with ..: for consistency and brevity? General Usage module	7	1212	April 3, 2020
Best way of `using` without bring names into scope? General Usage question , module	7	529	August 4, 2020

Combine using M: a, b; import M

Related topics