Closed ararslan closed 5 years ago
I'm inclined to just remove the Test
module then. This seems like an annoying property of julia namespacing, since we only care about the exports and overloaded macros.
Do you mean remove the functionality or just move it out of the submodule and into the main Memento module?
Move it out of the submodule and into the main Memento module. FWIW, submodules in julia just seem like more of a hassle than they're worth... which is pretty disappointing. I mostly blame using
.
The only problem seems to me to be that you can't import everything in Memento.Test
without importing the module Memento.Test
as Test
.
True, I just find that pretty annoying.
Since the Test stdlib module is no longer namespaced within Base, the
Test
identifier brought into scope uponusing Test
conflicts with that fromusing Memento.Test
, but in a weird, non-fatal way that somehow still seems to work.As an example, the following warning is emitted when running Memento's own tests:
We also get this warning when loading an internal package that depends on Memento, but I think this is just my fault from #109, inadvertently omitting Test from the Project.toml:
I would propose that
Memento.Test
be renamed toMemento.TestUtils
or similar.