Implicitly loaded modules in the future?

also maybe read the discussion here first, I think the include twice problem has been mentioned quite a few times, and not just me thinking this should be done automatically


and for whoever is looking for an actual package suffering from the include twice problem, I’m afraid there is none. When a package gets registered one has already workaround this by either splitting things out into packages or doing it by hand, I still remember some package authors would left a comment in their top module file like # do not change the include order, but I cannot remember which package is this, maybe someone could remind me.

I mean again isn’t this simply a human brain burden? why are we doing something that can be done automatically?

2 Likes