Default visibility not always working about slang HOT 3 CLOSED

Note that visiblity is related to module boundary, and not file boundary.

#include is just string pasting, so the compiler will always see duplicate definitions.

Users are avdvised to avoid #include whenever possible, and use import instead.

from slang.

And also, modules should always begin with a module name; declaration.
Without it, Slang treats the module as it is written in "legacy language".

In "legacy language", everything is public.

If you used any visiblity modifiers in the module, that also makes slang treat it as non-legacy.

from slang.

I thought, since #include in the module just pastes the code, the visibility should be the default module visibility (inside the module) in this example. Also thought that .slang on its own means it is a slang module. Your explanation makes total sense to me though.

I need the #include for preprocessor defines (not aware of a way to do this with modules) and stumbled upon this since, even though I had a #pragma once in the beginning of the header I got this collision with some typealiases.

from slang.