I am trying to define a method open in my own module. I have no interest in overloading Base.open and it’s not imported in my module. However, Travis now complains with: ERROR: LoadError: error in method definition: function Base.open must be explicitly imported to be extended I have never seen t…

I’m not familiar with how your package is built, but simply defining open does not mean Base.open is imported. It seems you are using Base.open in an included file though, is it possible that the deps/deps.jl file uses the definition from Base (e.g., open(<file>, <mode>))? $ cat tmp.jl module tmp …

Thanks for your help. You are right, the culprit was in an included file. The tricky part was that this method had been defined on the C++ side, and somehow the way that names are exported must have changed in CxxWrap. The relevant discussion happens here: https://github.com/JuliaInterop/CxxWrap.…

An open method does not have to be exported from Cxx for this to happen. Using the default open from Base in an included file is enough since Base is of course exporting open, see the example I provided. Further, the name clash does not happen with Cxx but with Base.

Trying not to overload Base.open

General Usage

jstrube April 12, 2020, 5:46am 5

Sure. In this case, however, there’s only one included file, deps.jl, which does not include Base.open or define any other method called open.

Topic		Replies	Views
Using isdefined to check where a function is defined General Usage cxx	15	1844	April 14, 2020
How to not import Base.isopen General Usage parsing , import , symbols , quoting	12	314	May 18, 2025
Overloading constructor New to Julia question , package	2	305	December 23, 2023
Inconsistent Base method overwrite behaviour General Usage	5	635	November 8, 2018
Extended method not being seen by original module General Usage	7	924	July 30, 2018

Trying not to overload Base.open

Related topics