The eval and include names are implicitly created by the core system to allow evaluating into a particular module inside of it without having to repeat the module name. Extending these builtin generic functions is currently allowed, although this is a bit of an accidental byproduct of the way they are defined and this may change in JuliaLang/julia#55949. If possible, I would suggest renaming the eval methods in this package to avoid implicitly extending the implicit methods. Alternatively, it is possible to suppress creation of the implicit methods by using baremodule (see e.g. phelipe/Fuzzy.jl#21 for that approach). I would have submitted a pull request, but I lack understanding of the organization of this package to decide which approach is the correct one.
The
evalandincludenames are implicitly created by the core system to allow evaluating into a particular module inside of it without having to repeat the module name. Extending these builtin generic functions is currently allowed, although this is a bit of an accidental byproduct of the way they are defined and this may change in JuliaLang/julia#55949. If possible, I would suggest renaming theevalmethods in this package to avoid implicitly extending the implicit methods. Alternatively, it is possible to suppress creation of the implicit methods by usingbaremodule(see e.g. phelipe/Fuzzy.jl#21 for that approach). I would have submitted a pull request, but I lack understanding of the organization of this package to decide which approach is the correct one.