<< 04-04-2025 >>

00:01:06FromDiscord<michaelb.eth> should be pretty easy to make a `doIt` template that would work like `mapIt` but have the purpose of forEach, i.e. for side effects
00:01:53FromDiscord<Elegantbeef> Isn't that just `apply`?
00:02:13FromDiscord<aintea> Yeah most of the things I'm going to put in that PR are small functions, most likely less than 5 lines of code, it's not hard to make them on my own but it's sad not to have them in the std
00:03:14FromDiscord<jackhftang> Curious to know what kind of helper functions you are itching to add to stdlib?
00:04:37FromDiscord<jackhftang> To me, stdlib is rather complete already
00:04:42FromDiscord<michaelb.eth> In reply to @Elegantbeef "Isn't that just `apply`?": that’s for mutating the input array, I thought
00:05:22FromDiscord<Elegantbeef> I suppose
00:06:05FromDiscord<Elegantbeef> `myCol.apply(proc(it: var T) = echo it)` works just fine though
00:06:34FromDiscord<michaelb.eth> yeah true
00:06:44FromDiscord<Elegantbeef> But not for immutable collections
00:07:06FromDiscord<Elegantbeef> I do sorta doubt anything like `foreach` getting into the stdlib at this point
00:41:40*rockcavera quit (Read error: Connection reset by peer)
00:42:00*rockcavera joined #nim
00:42:00*rockcavera quit (Changing host)
00:42:00*rockcavera joined #nim
01:59:54*ftajhii joined #nim
03:18:55*SchweinDeBurg quit (Quit: WeeChat 4.7.0-dev)
03:33:37*rockcavera quit (Remote host closed the connection)
03:49:49*SchweinDeBurg joined #nim
04:45:50*ntat joined #nim
05:09:36*syl_ is now known as syl
05:16:00*nils` quit (Ping timeout: 260 seconds)
06:03:27Amun-RaI noticed procs that could be funcs are still procs in stdlib
06:34:29*ntat quit (Quit: leaving)
07:15:33*CypherCat quit (Ping timeout: 248 seconds)
09:04:02*nils` joined #nim
09:36:58*amadaluzia joined #nim
10:01:49*Zevv joined #nim
10:01:58*Zevv left #nim (#nim)
10:37:18*amadaluzia quit (Remote host closed the connection)
10:37:42*amadaluzia joined #nim
12:49:51*ntat joined #nim
13:04:01*andy-turner joined #nim
13:15:23*nils` quit (Ping timeout: 244 seconds)
14:12:57*nils` joined #nim
14:25:34FromDiscord<Zoom> Most of small functions, including some already in stdLib, are just way of coping with incomplete support of basic functional idioms.↵(@aintea)
14:57:07*Arty is now known as Artea
15:51:39*amadaluzia quit (Ping timeout: 245 seconds)
15:51:56*amadaluzia joined #nim
16:11:46*amadaluzia quit (Ping timeout: 252 seconds)
16:28:21*CypherCat joined #nim
16:43:03*derpydoo joined #nim
16:53:12*nils` quit (Ping timeout: 252 seconds)
17:11:07FromDiscord<dawidek.2137> how do people cope with editor hints not propagating automatically between two files where one imports another on modification?
17:11:30FromDiscord<dawidek.2137> ie. I fix a compile time error in file a.nim, b.nim that imports it still shows errors unless I modify a character and save the file
17:11:54FromDiscord<dawidek.2137> (doesn't seem to vary between editors)
18:26:13*nils` joined #nim
18:43:17*andreas_ quit (Quit: Konversation terminated!)
18:43:31*andreas_ joined #nim
18:49:12*derpydoo quit (Ping timeout: 276 seconds)
19:19:26FromDiscord<nervecenter> In reply to @dawidek.2137 "ie. I fix a": Sounds like a nimsuggest/LSP issue, those are pretty common and both have been long in need for an overhaul. #tooling is the channel to discuss it. I've gotten a massive amount of work done without using it at all. Thankfully `nim check` will run a full error check and surface as many issues as it can, which is helpful.
19:20:07FromDiscord<nervecenter> (edit) "In reply to @dawidek.2137 "ie. I fix a": Sounds like a nimsuggest/LSP issue, those are pretty common and both have been long in need for an overhaul. #tooling is the channel to discuss it. I've gotten a massive amount of work done without using it at all. Thankfully `nim check` will run a full error check and surface as many issues as it can, which is helpful. ... " added "Other than that, editors have pretty decent tool
19:28:23*ntat quit (Quit: leaving)
19:28:31*GnuYawk quit (Quit: The Lounge - https://thelounge.chat)
19:28:50*GnuYawk joined #nim
19:47:52FromDiscord<starkiller1493> What's the best way of keeping track of used objects? I thought about using a hashtable with pointers but when I iterate over a sequence of them I seem to be getting a different pointer so I'm guessing it copies the object
19:51:50FromDiscord<Elegantbeef> "used objects"
19:54:21FromDiscord<starkiller1493> unfortunate wording 😁
19:55:14FromDiscord<demotomohiro> Pointers to a seq element become invalid pointer then the seq length is changed.
20:01:09FromDiscord<starkiller1493> i should have specified i'm not using directly the pointer to the object but to the object attribute
20:21:04*ftajhii quit (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
20:28:27*ftajhii joined #nim
20:29:09*andy-turner quit (Quit: Leaving)
20:44:03*zgasma quit (Quit: leaving)
20:44:12*zgasma joined #nim
23:49:20*beholders_eye quit (Ping timeout: 244 seconds)