<< 06-10-2025 >>
00:01:02FromDiscord<sunpoke04> okay, I think nim is not a good choice for this :d https://media.discordapp.net/attachments/371759389889003532/1424546960391540928/image.png?ex=68e4583e&is=68e306be&hm=c86bd4107aa9ef8d39238ec9357b93b873fca1c539c381e171bb19ff583c14ec&
00:07:22*Mister_Magister quit (Quit: bye)
00:09:56*Mister_Magister joined #nim
00:28:22FromDiscord<nervecenter> In reply to @sunpoke04 "okay, I think nim": Use Nimja templates
00:29:12FromDiscord<nervecenter> Make procs that take all the parameters, pass them to the templates. They're actual Nim templates that generate at compile time, so they'll be built into your final source.
00:30:06FromDiscord<nervecenter> And the nimja files are just HTML with some extra parameter-injection and conditional syntax on top
00:39:38FromDiscord<sunpoke04> In reply to @nervecenter "Use Nimja templates": that wouldn't fix the js problem though
01:14:17FromDiscord<nervecenter> nothing can fix the JS problem
02:00:05FromDiscord<sunpoke04> In reply to @nervecenter "nothing can fix the": maybe more js can fix the problem - js devs
02:28:08*xtr00 quit (Ping timeout: 256 seconds)
03:26:11*xtr00 joined #nim
04:41:33*lx12ucy quit (Remote host closed the connection)
06:27:35*SchweinDeBurg quit (Quit: WeeChat 4.8.0-dev)
06:28:02*SchweinDeBurg joined #nim
06:56:40*xtr00_ joined #nim
06:58:23*xtr00 quit (*.net *.split)
06:58:24*kasimir_ quit (*.net *.split)
06:58:25*Goodbye_Vincent1 quit (*.net *.split)
07:01:14*kasimir_ joined #nim
07:01:14*Goodbye_Vincent1 joined #nim
08:02:48*beholders_eye joined #nim
08:11:03FromDiscord<tearsinrain__> are there standard vector math packages similar to numpy in nim or i should just use nimpy bindings
08:22:09FromDiscord<lainlaylie> i think stuff like arraymancer and vmath
08:56:14FromDiscord<_.elias._> In reply to @tearsinrain__ "im building some high": Hi!, I write all my trading bots in Nim, relying heavily on the language’s async/await infrastructure.↵After long-running sessions I routinely hit the “too many open file descriptors” ceiling, so I am evaluating a future move to Chronos (the purely async runtime used by the Nim compiler itself) in the hope of eliminating that resource leak. Despite that the experience is very
08:59:21FromDiscord<ieltan> I dont think the nim compiler uses chronos 🤔
08:59:35FromDiscord<ieltan> https://github.com/status-im/nim-chronos
09:02:31FromDiscord<tearsinrain__> In reply to @_.elias._ "Hi!, I write all": hmm. would love to chat. im coming from python as well and have deep experience in it. im wondering about why you're hitting that issue and if its just sockets / ipc being opened or what
09:04:59FromDiscord<ieltan> asyncdispatch has all kinds of subtle issues unfortunately he's probably hitting one of leaking bugs plaguing it
09:06:44FromDiscord<ieltan> sounds like the program is not properly releasing file descriptors so they accumulate until the OS kills it
09:07:39FromDiscord<mitranim> In reply to @sunpoke04 "okay, I think nim": Maybe you want the Karax library
09:09:27FromDiscord<ieltan> btw it may not even be asyncdispatch fault and might just be the code itself :p
09:10:50FromDiscord<tearsinrain__> In reply to @ieltan "sounds like the program": right
09:11:13FromDiscord<tearsinrain__> but then a lot of sockets must be opened and closed rather than a few long running connections as well
09:11:36FromDiscord<tearsinrain__> so im wondering if its an engineering thing i can work around, something to be careful of (socket lifecycle management), or an actual problem with the library
09:12:48*anddam quit (*.net *.split)
09:12:48*computerquip quit (*.net *.split)
09:12:49*przmk quit (*.net *.split)
09:12:49*mal`` quit (*.net *.split)
09:12:49*attah quit (*.net *.split)
09:12:49*mahlon quit (*.net *.split)
09:14:21*anddam joined #nim
09:14:21*computerquip joined #nim
09:14:21*przmk joined #nim
09:14:21*mal`` joined #nim
09:14:21*attah joined #nim
09:14:21*mahlon joined #nim
09:16:39*computerquip quit (Ping timeout: 244 seconds)
09:17:23*computerquip joined #nim
09:21:02FromDiscord<0xfab_10> In reply to @_.elias._ "Hi!, I write all": > too many open file descriptors↵that's usually an OS limit thing. you can configure that limit. refer https://www.cogini.com/blog/tuning-tcp-ports-for-your-elixir-app/ (elixir because that's the one I had). has some links to other resources
09:21:45FromDiscord<0xfab_10> assuming you're properly handling all your file descriptors that is
09:21:53FromDiscord<0xfab_10> so you might wanna check for a leak first
10:27:59*marcus quit (Ping timeout: 265 seconds)
10:28:15*cornfeedhobo quit (Ping timeout: 245 seconds)
10:28:15*lucerne9 quit (Ping timeout: 245 seconds)
10:28:37*marcus joined #nim
10:28:40*Jjp137 quit (Ping timeout: 256 seconds)
10:28:59*Jjp137 joined #nim
10:29:14*Amun-Ra quit (Ping timeout: 256 seconds)
10:29:40*Amun-Ra joined #nim
10:30:18*lucerne9 joined #nim
10:31:35*madprops quit (Ping timeout: 245 seconds)
10:32:21FromDiscord<blackmius> In reply to @sunpoke04 "okay, I think nim": i see only thing in your buttons changing is first arg and then an id, why wouldnt you create a function which will return a button?
10:32:28*madprops joined #nim
10:32:28*madprops quit (Changing host)
10:32:28*madprops joined #nim
10:33:17*cornfeedhobo joined #nim
10:36:02*strogon14 quit (Ping timeout: 256 seconds)
10:36:11*strogon14 joined #nim
10:41:18FromDiscord<blackmius> In reply to @tearsinrain__ "so im wondering if": recently i found one, sockets in http library just have not been closing until OS kills process
10:43:01FromDiscord<blackmius> https://github.com/nim-lang/Nim/issues/24943
10:44:40FromDiscord<blackmius> workaround is to close everything yourself
11:00:20*Ekho quit (Ping timeout: 245 seconds)
11:01:35*bcksl quit (Ping timeout: 245 seconds)
11:08:08*bcksl joined #nim
11:08:13FromDiscord<sunpoke04> In reply to @blackmius "i see only thing": I mean, I was still testing also that code didn't work, so I was just trying things mindlessly
11:13:55*Ekho joined #nim
11:16:42*Mister_Magister_ joined #nim
11:17:08*Mister_Magister quit (Ping timeout: 256 seconds)
11:19:36*Mister_Magister_ is now known as Mister_Magister
11:37:55FromDiscord<_.elias._> In reply to @fabric.input_output "so you might wanna": had debugging sessions and blamed the other side. is not a problem for me but with time i'll like to migrate to chronos. (or async with cps if it comes with Nim3).
11:55:36*xet7 joined #nim
12:00:28*xet7 quit (Ping timeout: 256 seconds)
12:12:08*xet7 joined #nim
13:42:14*lucerne9 quit (Ping timeout: 256 seconds)
13:43:26*lucerne9 joined #nim
14:13:49*xutaxkamay quit (Ping timeout: 264 seconds)
14:53:33*xutaxkamay joined #nim
16:17:57*beholders_eye quit (Ping timeout: 260 seconds)
16:33:28*beholders_eye joined #nim
16:54:07*beholders_eye quit (Ping timeout: 260 seconds)
17:39:07*beholders_eye joined #nim
17:51:11FromDiscord<treeform> Does any one know how to make config.nims run some thing after the exe is finished compiling? emrun or signing the already compiled binary?
17:51:26*cwiggins123 joined #nim
17:55:09FromDiscord<treeform> Or know how to make `nim r -d:emscripten foo.nim` use `emrun` instead of running the wasm file wich fails?
17:57:24FromDiscord<Elegantbeef> Fork the compiler to add a `--wasmRuntime:emrun` 😄
17:59:57FromDiscord<treeform> Forking will work for me, but this is more for other people?
18:01:00FromDiscord<Elegantbeef> When you fork it you PR the change to the compiler and hope it's adopted
18:01:12FromDiscord<Elegantbeef> Otherwise make a `config.nims` with a task that is build and run
18:10:13*beholders_eye quit (Ping timeout: 256 seconds)
18:11:51*beholders_eye joined #nim
18:26:06*beholders_eye quit (Ping timeout: 256 seconds)
18:31:30*cwiggins123 left #nim (#nim)
18:46:34*switchy_ joined #nim
18:47:04*end quit (Ping timeout: 248 seconds)
18:47:55*switchy quit (Ping timeout: 248 seconds)
18:47:56*switchy_ is now known as switchy
18:53:20*end joined #nim
18:55:59FromDiscord<kiloneie> ? eh ? https://media.discordapp.net/attachments/371759389889003532/1424832575247093780/Screenshot_2025-10-06_20-55-44.png?ex=68e5623e&is=68e410be&hm=0340f47be22fa03086fe4e1569622860a307833230f2f8fcd19dd71cfb53d069&
18:58:50Amun-Rakiloneie: use delete with a slice
18:59:03Amun-Raas deprecated message states :)
19:00:21FromDiscord<kiloneie> Oh, i use the name range, not slice
19:00:27FromDiscord<kiloneie> remove comma, add the dots!
19:01:19FromDiscord<kiloneie> Whats the style guide on ranges ? like this, or with spaces around the .. dots ? `delete(mainModuleName, fileName.low..appDir.high+1)`
19:02:11FromDiscord<lainlaylie> that should be `delete(mainModuleName, fileName.low .. appDir.high + 1)`
19:02:19Amun-Rarunnable examples do not use spaces around '..' but I don't like it; I use spaces
19:02:59FromDiscord<lainlaylie> or rather `mainModuleName.delete(fileName.low .. appDir.high + 1)`
19:03:12Amun-Rahttps://github.com/nim-lang/Nim/blob/devel/lib/pure/strutils.nim#L1576-L1582
19:04:44FromDiscord<kiloneie> In reply to @lainlaylie "or rather `mainModuleName.delete(fileName.low ..": I like that, it's how i usually did it, though sometimes i question it...
19:06:14FromDiscord<kiloneie> it's i feel like this is simple enough to not use spaces `mainModuleName.delete(fileName.low..appDir.high+1)` , but tougher examples, that's where i need my spaces. Spaces after arguments is mandatory.
19:07:05FromDiscord<Elegantbeef> The rule is generally if there is an expression you put spaces around the `..` operator
19:07:47FromDiscord<Elegantbeef> so it's `a..b` but `a .. b + 1`
19:08:49FromDiscord<kiloneie> Okay fine D:
19:20:49*beholders_eye joined #nim
20:25:13*beholders_eye quit (Ping timeout: 264 seconds)
21:52:34*rockcavera joined #nim
22:30:36*Lord_Nightmare2 joined #nim
22:30:54*Lord_Nightmare quit (Read error: Connection reset by peer)
22:32:38*Lord_Nightmare2 is now known as Lord_Nightmare