I’m encountered with a fairly strange circumstance where the names that are not exported from a package can also be imported into another project environment. Detail: There is a package named MyPkg that is just in development. In this package, function f has been exported explicitly with export f, …

If I understand correctly, you want to use Y.f as f only from within X, and you want to use X.g as g outside of f. If so, then just don’t re-export. Reexport is a convenience for exporting everything. If that’s not want you want, then explicitly export what you do want. From GitHub - simonster/R…

Names that are not exported from a package can also be imported into another project

General Usage

WuSiren April 3, 2024, 1:39pm 17

Thank you, for me it finally makes sense, although I still feels a bit strange.

Topic		Replies	Views
Exporting symbols of imported module General Usage	5	1852	January 16, 2019
Is Julia able to export a module as another (aliased) name? General Usage question , package , development	1	1122	November 7, 2019
Is an explicit "export" a good thing? General Usage	51	5876	December 7, 2017
Reexporting problem types General Usage question , module , design	3	738	August 31, 2017
`import` can’t load just-defined modules? Can’t re-`export` in-module functions? New to Julia question	4	1468	June 9, 2017

Names that are not exported from a package can also be imported into another project

Related topics