<< 01-05-2026 >>

00:39:19*alexdaguy quit (Quit: w)
01:05:14*xet7 quit (Ping timeout: 248 seconds)
01:17:27*xet7 joined #nim
02:53:04*rockcavera joined #nim
03:15:26*ephapticpulse quit (Quit: ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.3))
03:35:59*rockcavera quit (Remote host closed the connection)
03:42:40*rockcavera joined #nim
04:25:31*xet7 quit (Remote host closed the connection)
04:41:37*deavmi quit (Read error: Connection reset by peer)
04:42:12*deavmi joined #nim
04:45:57*PMunch joined #nim
04:48:55*PMunch__ quit (Ping timeout: 245 seconds)
05:20:54*Jjp137 quit (Remote host closed the connection)
05:25:16*Jjp137 joined #nim
06:33:11FromDiscord<nevillegg> In reply to @mostypc123 (linkin park lover) "talking about that it": Cpp is always slow.
06:33:22FromDiscord<nevillegg> Maybe intel compiler could fix that problem.
07:00:25*oisota2 joined #nim
07:01:20*tiorock joined #nim
07:01:20*tiorock quit (Changing host)
07:01:20*tiorock joined #nim
07:01:20*rockcavera is now known as Guest3668
07:01:20*Guest3668 quit (Killed (molybdenum.libera.chat (Nickname regained by services)))
07:01:20*tiorock is now known as rockcavera
07:02:07*oisota quit (Ping timeout: 264 seconds)
07:02:07*oisota2 is now known as oisota
08:13:31*pmp-p quit (Ping timeout: 264 seconds)
08:28:45*pmp-p joined #nim
08:41:24*oprypin quit (Quit: Bye)
08:41:48*oprypin joined #nim
08:46:27*adigitoleo quit (Ping timeout: 255 seconds)
08:47:41*adigitoleo joined #nim
08:53:11*xet7 joined #nim
08:55:43FromDiscord<[Next-System] systemblue> is it true that nim's mm:none can do automatic memory management for dynamic memory by defining destroiers(=destroy)?↵I heard that Nim has RAII and compiler injects destroier after variable's lifetime scope is over↵so is it true that most time, Nim can use automatic memory management for dynamic memory by defining destroiers
08:57:38FromDiscord<crochubourbier> sent a long message, see https://pasty.ee/bszhGtMF
08:58:54FromDiscord<crochubourbier> (edit) "https://pasty.ee/IweADjou" => "https://pasty.ee/nDyXqKtX"
08:59:29FromDiscord<crochubourbier> (edit) "https://pasty.ee/ITumaMdT" => "https://pasty.ee/RxgWYJVP"
09:04:00FromDiscord<crochubourbier> In reply to @bluewhale_unkown_x "is it true that": The GC is what's deciding when to call those destroy functions
09:05:03FromDiscord<[Next-System] systemblue> so someone told me that Nim's mm:none with destroy funtion is same with Rust with out AtomicRC, RC
09:05:44FromDiscord<crochubourbier> This is ARC i think
09:05:57FromDiscord<crochubourbier> or maybe im wrong
09:06:34FromDiscord<[Next-System] systemblue> In reply to @crochubourbier "The GC is what's": some languages call destroy function in compile time with out GC by scope controlling like C++↵and now, Nim is not GC Lang
09:08:03FromDiscord<crochubourbier> end of scope deletion is basically what ARC memory mode is I believe
09:08:17FromDiscord<crochubourbier> lemme check this real quick
09:08:41FromDiscord<[Next-System] systemblue> I should know correct answer about that ↵because I have mind to compile my program to none with out manual memory management↵if it's impossible, I should make semi auto destroier and lifetime scope checker with macro
09:09:39FromDiscord<[Next-System] systemblue> I mean is it samely work in none too?
09:10:02FromDiscord<crochubourbier> sent a code paste, see https://play.nim-lang.org/#pasty=DUjLvzlI
09:10:25FromDiscord<crochubourbier> (edit) "https://play.nim-lang.org/#pasty=msUuApRE" => "https://play.nim-lang.org/#pasty=JTWMinXQ"
09:11:03FromDiscord<crochubourbier> you can still use defer I think
09:11:11FromDiscord<[Next-System] systemblue> I mean defining destroy function might be worked ↵because it's not GC↵it's comp time RAII
09:12:00FromDiscord<crochubourbier> give it a try then, I didn't test it
09:12:15FromDiscord<[Next-System] systemblue> please contact me if there's someone who knows details about mm:none and destroy function
09:15:02FromDiscord<crochubourbier> https://nim-lang.org/docs/mm.html
09:22:05*przmk_ quit (Ping timeout: 252 seconds)
09:22:10*przmk___ joined #nim
09:30:21*oprypin quit (Quit: Bye)
09:30:47*oprypin joined #nim
09:31:19FromDiscord<planetis_m> In reply to @bluewhale_unkown_x "please contact me if": Easy way to test it. Compile a sample program with --expandArc:main with --mm:none and without. See if destructors are missing
09:33:31FromDiscord<planetis_m> In reply to @crochubourbier "Hey guys, I've been": Stick with case statements? Covering all cases? The new sum types will make accessing case'd fields outside a case statement illigal anyway.
09:57:53FromDiscord<crochubourbier> In reply to @planetis_m "Stick with case statements?": The whole point of what is that if your function is called inside a case statement you need to have another case or assert statement in the body of the function, what I want to so is being able to take already narrowed arguments in functions
09:58:06FromDiscord<crochubourbier> (edit) "In reply to @planetis_m "Stick with case statements?": The whole point of what ... is" added "Im saying"
09:58:55FromDiscord<crochubourbier> (edit) "statement" => "statement, and the type is already narrowed at call site," | "have another case or assert statement" => "narrow it a second time" | "so" => "do"
09:59:08FromDiscord<crochubourbier> (edit) "statement," => "statement"
09:59:17FromDiscord<crochubourbier> (edit) "In reply to @planetis_m "Stick with case statements?": The whole point of what Im saying is that if your function is called inside a case statement and the type is already narrowed at call site, you ... need" added "still"
09:59:54FromDiscord<crochubourbier> so that the function can be called only with specific nodes as arguement
10:01:50FromDiscord<crochubourbier> (edit) "nodes" => "variant" | "variantas arguement ... " added "and dont accept any kind"
10:14:38*SchweinDeBurg quit (Quit: WeeChat 4.8.0-dev)
10:38:29FromDiscord<planetis_m> I thought so yes
10:51:58*beholders_eye joined #nim
11:08:42*przmk___ quit (Remote host closed the connection)
11:10:52*przmk joined #nim
11:17:42*beholders_eye quit (Ping timeout: 255 seconds)
11:59:03*PMunch_ joined #nim
12:01:48*PMunch quit (Ping timeout: 255 seconds)
13:36:09*deavmi quit (Read error: No route to host)
13:39:12*deavmi joined #nim
13:40:54*deavmi quit (Client Quit)
13:43:18*deavmi joined #nim
13:47:49*deavmi quit (Remote host closed the connection)
13:50:04*deavmi joined #nim
14:40:40*xet7 quit (Remote host closed the connection)
14:54:17FromDiscord<crochubourbier> So you didnt solve my problem 😂
16:36:40FromDiscord<planetis_m> In reply to @crochubourbier "So you didnt solve": Dont overthink this, do not go looking for magic solutions without clear benefit, that dont hold their weight?
16:37:23*fwinter joined #nim
16:38:20*fwinter left #nim (nim)
17:09:33FromDiscord<toitle3554> In reply to @crochubourbier "Hey guys, I've been": could try using a bunch of `distinct` types instead of variants, just gets hard to store those objects in arrays
17:12:14FromDiscord<toitle3554> sent a code paste, see https://play.nim-lang.org/#pasty=GCVtSVsm
17:12:38FromDiscord<toitle3554> probably incorrect syntax but you get the idea
17:13:40FromDiscord<toitle3554> (edit) "https://play.nim-lang.org/#pasty=RvzjobkK" => "https://play.nim-lang.org/#pasty=fSyxAfNs"
17:16:17anddamAmun-Ra: codex to the rescue
17:16:22anddam```I’m replacing the macro-style imports with the underlying windowed functions that PDCurses actually exports. That should remove the
17:16:25anddam could not import: getch failure and avoid the same problem on the next UI call.```
17:16:39anddamit wasn't bitness after all
17:16:53anddamI had it write a winget frontend using ncurses
17:34:00*beholders_eye joined #nim
18:32:18*SchweinDeBurg joined #nim
19:09:17FromDiscord<crochubourbier> In reply to @toitle3554 "could try using a": I used distinct types but I managed to pull off something even better with a custom case macro:↵https://play.nim-lang.org/#pasty=BPolVoXB
19:09:26FromDiscord<crochubourbier> (edit) "In reply to @toitle3554 "could try using a": I used distinct types but I ... managed" added "finally"
19:10:02FromDiscord<crochubourbier> it may not be the best way of writing the macro, but it works as expected
19:11:34FromDiscord<crochubourbier> but I still have to assume that the user won't construct the distinct type himself by hand
19:12:51FromDiscord<crochubourbier> because sadly we cannot override the default constructor of a type
19:13:00FromDiscord<crochubourbier> (i think)
19:18:04*ftajhii quit (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
19:19:30FromDiscord<crochubourbier> Anyways that's why I love Nim so much, when you feel that a language feature is missing, you can just implement it 😂
19:20:08FromDiscord<crochubourbier> (edit) "Anyways that's ... why" added "one of the reasons"
19:30:13*ftajhii joined #nim
19:44:27*amadaluzia quit (Read error: Connection reset by peer)
19:59:09*amadaluzia joined #nim
20:00:48*amadaluzia quit (Read error: Connection reset by peer)
20:14:37*amadaluzia joined #nim
20:46:57*PMunch_ quit (Ping timeout: 255 seconds)
21:03:22*gabreal quit (Quit: Cleanly disconnecting(pray for me))
21:29:43*amadaluzia quit (Ping timeout: 264 seconds)
21:30:38*amadaluzia joined #nim
22:12:44*xet7 joined #nim
22:22:53FromDiscord<capocasa> In reply to @mratsim "<@378612300426248212> this is annoying": Just saw your messages here, I'm not on discord that often.↵↵Sorry about that!!! I was exploring how some issue triaging could be autoated, but I didn't consider github would consider each username a mention and notify you.
22:25:20FromDiscord<capocasa> In reply to @planetis_m "What kind of feedback": Sorry again! It was purely an accident- I uploaded some issues in my own project to experiment with classification as a scratch space to develop a proposal for some issue automation- I didn't consider github consider each name a mention.
22:41:18*karolyi quit (Remote host closed the connection)
22:46:59*karolyi joined #nim
23:15:41*xet7 quit (Remote host closed the connection)
23:17:07*xet7 joined #nim
23:26:39*syl quit (Quit: C-x C-c)
23:36:49*syl joined #nim
23:57:19*syl quit (Ping timeout: 276 seconds)