<< 21-02-2026 >>

01:07:10*zodman quit (Ping timeout: 256 seconds)
01:09:03*zodman joined #nim
01:10:58*zodman quit (Client Quit)
02:00:55*beholders_eye quit (Ping timeout: 264 seconds)
02:13:56*zodman joined #nim
07:11:20*mrinsane quit (Ping timeout: 268 seconds)
11:13:34*beholders_eye joined #nim
14:24:29*benson joined #nim
15:11:06*zodman2 joined #nim
18:49:28*benson quit (Quit: Konversation terminated!)
19:07:56*mrinsane joined #nim
19:12:24*mrinsane quit (Ping timeout: 245 seconds)
19:56:13*_________ quit (Server closed connection)
19:56:34*_________ joined #nim
20:02:55*mrinsane joined #nim
20:03:53mrinsanei'm I correct in understanding that when importing a module symbols from that module are dumped into the global namespace?
20:04:05mrinsaneis there a way to have more control over that?
20:05:01mrinsanespecifically to say "import these symbols but keep them behind the <modulename> symbol"
20:17:14*yeti quit (Quit: \\//_)
20:17:37*yeti joined #nim
20:54:32strogon14you can always refer to symbols with <modulename>.<symbol>.
20:54:32strogon14and you can do "from <module> import <symbol>"
20:54:32strogon14Lastly, you can do "from <module> import nil", which is what you where asking about, but imho it's rarely necessary.
20:54:58strogon14https://nim-lang.org/docs/manual.html#modules-from-import-statement
20:55:19strogon14mrinsane: ^^^
20:59:58mrinsanethanks!
21:00:36mrinsaneyes I noticed that I can access a symbol directly or via module.symbol
21:00:58mrinsanewhy do you think it's rarely necessary?
21:01:23mrinsanebecause polymorphism allows you to call the correct function so don't sweat it?