<< 06-04-2026 >>

00:11:40*Mister_Magister quit (Quit: bye)
00:14:24*Mister_Magister joined #nim
02:09:27*krunsh quit (Quit: WeeChat 4.7.2)
02:10:29*Jjp137 joined #nim
04:01:59*hygo quit (Ping timeout: 244 seconds)
04:03:57*hygo joined #nim
06:07:08*mrinsane quit (Ping timeout: 252 seconds)
07:45:29*hygo quit (Quit: WeeChat 4.7.1)
07:54:57*beholders_eye joined #nim
08:59:21*lumidify quit (Ping timeout: 248 seconds)
08:59:38*lumidify joined #nim
09:06:26*Mister_Magister quit (Ping timeout: 252 seconds)
09:06:49*Mister_Magister joined #nim
09:41:12*minime joined #nim
10:07:50minimeHello, does anyone have information for me on the nimcache ( ~/.cache/nim/* )? I understand that I can remove it at will, however I would like to know if there are best practices for managing nim's cache. Any and all information is much appreciated.
10:13:52FromDiscord<nnsee> In reply to @minime "Hello, does anyone have": there isn't any functionality like this built into the compiler, no. users are generally expected to manage their own cache. personally, i point my nimcache to a tmpfs (backed by RAM) meaning reading/writing cache is fast and cache doesn't accumulate as the files are obviously gone when i reboot. you're free to use any of the common methods for managing .cache, like using systemd's `user-tmpf
10:16:21FromDiscord<nnsee> don't quote me on this, but i believe some distros already include this by default (check your `/usr/share/user-tmpfiles.d/` i suppose)
10:26:02minimeThat's what I suspected, that there is no functionality built into nim. Thank you for confirming this. I don't use systemd, but there's, like you already said, a lot of ways to manage such cache and temporary directories. Thank you for helping me.
13:08:58FromDiscord<Zoom> Wait, is nimble.directory down again or is it down still? Last time I noticed was a couple weeks ago.