<< 12-07-2026 >>
01:50:50*Lord_Nightmare quit (Quit: ZNC - http://znc.in)
03:02:30*Skippy8 joined #nim
03:21:54*Skippy8 quit (Ping timeout: 248 seconds)
05:44:10*Lord_Nightmare joined #nim
06:15:24FromDiscord<Laylie> news to me. we have enum overloading anyway.
06:30:19*alexdaguy joined #nim
06:58:13*alexdaguy quit (Quit: w)
12:54:21FromDiscord<narimiran> sent a long message, see https://pasty.ee/aPUvkBCj
12:58:35FromDiscord<helwastaken> Is 2.2.x gonna get more updates?
13:20:53FromDiscord<11clock> What happened to 2.3?
14:17:52FromDiscord<narimiran> In reply to @helwastaken "Is 2.2.x gonna get": Yes.
14:33:29FromDiscord<_timurski> In reply to @narimiran "Nim 2.4.0 **release candidate**": cool! gonna make a small neovim plugin to work with nim track
14:42:45*amadaluzia quit (Read error: Connection reset by peer)
14:55:05*amadaluzia joined #nim
15:29:51*Skippy8 joined #nim
15:34:22*Skippy8 quit (Ping timeout: 252 seconds)
15:34:59*Skippy8 joined #nim
15:44:20*termer quit (Remote host closed the connection)
15:45:52*termer joined #nim
16:00:01FromDiscord<11clock> So nim track is specifically for a non-LSP workflow?
16:05:37*Skippy8 quit (Ping timeout: 276 seconds)
16:06:16*Skippy8 joined #nim
16:46:12*Skippy8 quit (Ping timeout: 256 seconds)
16:59:45FromDiscord<_timurski> the current nim lsp's are awful to use for me, in my experience they've been crazy unstable and memory intensive
17:00:12FromDiscord<_timurski> i already work perfectly fine without an LSP but i think i can gain a lot from nim track + nim check with just a simple neovim plugin
17:00:20FromDiscord<_timurski> (edit) "i already work perfectly fine without an LSP but i think i can gain a lot from nim track + nim check ... with" added "+ nimpretty"
17:00:26FromDiscord<_timurski> and now that nim track is out i have the motivation to do that
17:00:42FromDiscord<_timurski> (edit) "gain a lot" => "some qol"
17:02:42*sdothum quit (Remote host closed the connection)
17:04:51*sdothum joined #nim
17:43:31Amun-RaI have two large..ish nim projects
17:44:11Amun-Raand I have dedicated build aliases for each: alias pmake='killall -9 nimsuggest; make -C /path/to/project'
17:44:16Amun-Rathat tells a lot ;)
17:44:27Amun-RaI use neovim + lsp
17:44:40Amun-Ranimsuggest hogs cpu and ram a lot
17:49:25Amun-RaI stopped using nimble - it fails to build on systems that nimble doesn't support nightlies for (which makes no sense)
17:52:58Amun-RaI rarely file a PR/bug reports; I usually write patches; like with repr - I have my own repr, nim one is broken
17:53:03Amun-Ra(\r)
17:53:46FromDiscord<_timurski> ):
17:54:28Amun-RaI mean either \r or \n advances to the next line; I don't remember which one
17:54:39*Skippy8 joined #nim
17:58:08Amun-Rahttps://play.nim-lang.org/#pasty=KfUWhStq
18:04:21*Skippy8 quit (Ping timeout: 268 seconds)
18:47:03FromDiscord<_timurski> nim check and nim track, pretty shrimple https://media.discordapp.net/attachments/371759389889003532/1525936542382555196/2026-07-12_11-46-17.mp4?ex=6a5532a6&is=6a53e126&hm=9a170ff10eba2ea6cd8264ab76ed45712901433e9c648be4ea147229672ff7ec&
18:48:05FromDiscord<_timurski> https://media.discordapp.net/attachments/371759389889003532/1525936799858557090/Screenshot_2026-07-12_at_11.47.51_AM.png?ex=6a5532e3&is=6a53e163&hm=52ffb187374076bd87b0cd0c082fef2b7009c101d8a3d8044447b9d97e050618& https://media.discordapp.net/attachments/371759389889003532/1525936800210751559/Screenshot_2026-07-12_at_11.47.47_AM.png?ex=6a5532e3&is=6a53e163&hm=c632cdc29ed68f9da91036f4e016ecda0e846fb1708b2e739ed8f07bb71d35ca&
18:48:21FromDiscord<_timurski> extremely basic but doesn't have any running process and such... so very little downside
18:48:50*joast quit (Quit: Leaving.)
18:49:41*sdothum quit (Remote host closed the connection)
18:51:41*sdothum joined #nim
19:07:19*Skippy8 joined #nim
19:11:50*Skippy8 quit (Ping timeout: 256 seconds)
19:26:34FromDiscord<11clock> I think I am getting more used to 2 space indentation. Rainbow indents helps
19:27:58*joast joined #nim