On Thursday, 4 December 2014 at 10:37:12 UTC, Robert burner
Schadek wrote:
That is much nicer, thank you for taking the time.
Couldn't way just say that we don't import __MODULE__ but
rather __MODULE__ ~ "_loggerinfo.d" and then describe the
import constraint in the documentation.
Importing a different module wouldn't reliably work, when file
paths differ from module paths.
The nice thing about importing __MODULE__ is that the compiler
already knows it, because it's the caller.
Also importing a different file by name feels a bit too much like
magic ruby bindings.
