<< 05-06-2025 >>

00:12:23FromDiscord<user2m> In reply to @battery.acid.bubblegum "What have you tried,": An interesting, ambitious but unfinished template library called Tim. Hot reloading by putting all my templates in dlls (which worked most of the time but would occasionally segfault. I'm guessing due to something async) and I'm working on hot reloading scf files now
00:12:38FromDiscord<leorize> you can do poor man's HCR
00:12:50FromDiscord<leorize> use a watcher or something, rebuild and restart the program
00:13:27FromDiscord<leorize> that's more or less how something like https://github.com/air-verse/air works
00:13:32FromDiscord<leorize> and it's better than nothing
00:18:21FromDiscord<Robyn [She/Her]> In reply to @user2m "An interesting, ambitious but": yeah use Nim RTL and use setGlobalDispatcher, and if you gotta unload the library, try and make sure you clean everything up where possible
01:32:15FromDiscord<nitely_> In reply to @user2m "has anyone figured out": there is https://github.com/enthus1ast/nimja/tree/master?tab=readme-ov-file#automatic-recompilation--hot-code-reloading-hcr the example uses jester (similar to prologue)
01:59:52FromDiscord<user2m> I'll explore all these in the next coming weeks thanks !
02:17:11*amadaluzia quit (Quit: ZNC 1.9.1 - https://znc.in)
03:38:24*rockcavera quit (Remote host closed the connection)
03:47:11*marcus quit (Remote host closed the connection)
03:49:27*marcus joined #nim
04:03:45*SchweinDeBurg joined #nim
05:19:09*ntat joined #nim
06:23:34*andy-turner joined #nim
06:23:59*andy-turner quit (Remote host closed the connection)
06:57:53*nils` quit (Ping timeout: 268 seconds)
07:45:02*xet7 joined #nim
07:45:23*nils` joined #nim
08:46:34FromDiscord<hawkey5212> sent a long message, see https://pasty.ee/UPdBBWwi
08:57:24*beholders_eye joined #nim
09:03:06*xutaxkamay quit (Ping timeout: 272 seconds)
09:03:33*xutaxkamay joined #nim
09:26:34*andy-turner joined #nim
09:41:54*ntat quit (Quit: leaving)
10:20:56FromDiscord<xtrayambak> Is there a way to prevent Nim from emitting `#line` macros in C/C++? It makes debugging bad FFI a pain in the rear end.
10:37:09*ntat joined #nim
10:52:40*m5zs7k quit (Remote host closed the connection)
10:53:39*m5zs7k joined #nim
11:40:07FromDiscord<griffith1deadly> In reply to @xtrayambak "Is there a way": `--linetrace:off`?
13:37:26FromDiscord<griffith1deadly> beef, is `toTrait` makes a copy for `object`? and what's about `ref object`?
13:49:59FromDiscord<nitely_> In reply to @hawkey5212 "A project I'm working": Open an issue in nim-libp2p describing the problem. Stick to the previous libp2p version meanwhile or fork and remove the constraint
13:59:18FromDiscord<nitely_> In reply to @hawkey5212 "A project I'm working": you can also try adding "chronicles == 0.10.3" to your nimble. Do you require "chronicles == 0.11" in your nimble or dependencies? otherwise nimble should be able to resolve the dependency issue
14:01:02FromDiscord<nitely_> (edit) "nimble." => "nimble file." | "nimble file.Do you require "chronicles == 0.11" in your nimble ... orif" added "file" | "otherwise" => "if not"
14:03:37*ntat quit (Quit: leaving)
14:31:30FromDiscord<hawkey5212> sent a long message, see https://pasty.ee/fEjxXSMk
14:59:41FromDiscord<Phil> In reply to @hawkey5212 "I'm currently working it": Huh, I typically love nimbledeps because in the meantime I can just change the code inside nimbledeps while I wait for the lib to fix things
15:04:32FromDiscord<hawkey5212> In reply to @isofruit "Huh, I typically love": What I wish I could do, is clone the repo localy, and set the path in my .nimble file, so you could just do `requires chronicles = "path/to/chronicles" and you're done.↵↵Makes no sense to me that you can fall back to a github url, but cant fallback to a file url, but maybe what's "normal" to me as someone that's used to rust is actually non-trivial.
15:05:24FromDiscord<Phil> In reply to @hawkey5212 "What I wish I": Strictly speaking you can fork and reference your specific fork in your nimble file if need be
15:05:36FromDiscord<Phil> Since you're forking anyhow means you have a remote fork
15:05:40FromDiscord<Phil> So close enough (?)
15:05:49FromDiscord<Phil> (edit) "Since you're forking anyhow means you ... have" added "can easily"
15:07:34FromDiscord<hawkey5212> sent a long message, see https://pasty.ee/EWCUoKlc
15:07:59FromDiscord<Phil> Hmmm checked out the --path flag yet then?
15:08:51FromDiscord<Phil> Been a while since I needed to get deeper into the nimble weeds
15:09:51FromDiscord<Phil> Ahhh I still use it in a place, I used to have my own local version of norm and specified this path flag during compilation in order to ensure that it is being used as the norm dependency instead of anything else:↵`--path:/home/philipp/.nimble/pkgs2/norm-2.7.0-00a93c0f5628651c98c933909f3c3c3cd17696f0`
15:10:12FromDiscord<hawkey5212> sent a long message, see https://pasty.ee/VqwhZoiE
15:11:14FromDiscord<Phil> I ain't saying it's perfect, I'm saying this was the best I came up with back in the day before I got to my current setup 😄
15:11:42FromDiscord<hawkey5212> in rust its just:↵↵`foo = {path = "path/to/project"}` and you're good. I would prefer standard url, such as `foo = "path://path/to"`, but still.
15:12:41FromDiscord<hawkey5212> I'm new to nim, and the language itself has some interesting ideas, but the tooling, both in terms of whats lacking, and in terms of design decisions leaves a _lot_ to be desired in my experience so far 😦
15:28:46FromDiscord<lainlaylie> `nimble develop -a:...` has worked for me
15:29:59FromDiscord<lainlaylie> (side note: i find the idea of having local paths in a nimble file questionable because usually we want nimble files to work across machines)
15:57:10FromDiscord<hawkey5212> it's for dev purposes. Can also be handy when you hav a mono-repo. the path "../foo", where `..` is your project root dir, and `.` is the root directory of one independant library within your project
15:57:16FromDiscord<hawkey5212> I've seen it work quite nicely
15:59:10*beholders_eye quit (Ping timeout: 244 seconds)
16:18:48*attah quit (Ping timeout: 244 seconds)
16:22:00*attah joined #nim
16:55:20FromDiscord<nitely_> for dev I used to do "nimble develop -g" on the local package and it would be used by any local package depending on it, but that feature has been broken since forever https://github.com/nim-lang/nimble/issues/1124
16:58:08*SchweinDeBurg quit (Quit: WeeChat 4.7.0-dev)
16:59:00*ntat joined #nim
16:59:19*amadaluzia joined #nim
17:43:49*amadaluzia quit (Read error: Connection reset by peer)
17:44:01*amadaluzia_ joined #nim
17:45:53*nils` quit (Ping timeout: 248 seconds)
17:46:45*nils` joined #nim
19:38:56*ntat quit (Quit: leaving)
19:39:04*andy-turner quit (Read error: Connection reset by peer)
19:39:17*andy-turner joined #nim
20:18:41*amadaluzia_ quit (Quit: ZNC 1.9.1 - https://znc.in)
20:35:52*nils` quit (Quit: nils`)
20:58:00FromDiscord<nocturn9x> In reply to @isofruit "Not beyond just looking": I can't seem to get one lol
20:58:05FromDiscord<nocturn9x> hottie fails
21:11:49*andy-turner quit (Quit: Leaving)
21:12:16FromDiscord<Elegantbeef> If on linux use hotspot
21:12:27FromDiscord<Elegantbeef> Just a wrapper over perf but it works well
21:12:35*rockcavera joined #nim
21:18:50*andy-turner joined #nim
21:22:18*nils` joined #nim
21:26:06*andy-turner quit (Quit: Leaving)
21:27:55FromDiscord<ricky._.spanish> anyone know if theres a nim binding for clay ui library?
21:28:40FromDiscord<ricky._.spanish> (edit) "anyone know if theres a nim binding for clay ui library? ... " added "was trying to generate it using furthark but honestly getting it to build on github codespaces was a pain"
21:32:19FromDiscord<0xfab_10> you're trying to do the futhark codegen in github codespace?
21:40:22*rockcavera is now known as Guest5836
21:40:22*tiorock joined #nim
21:40:22*Guest5836 quit (Killed (zinc.libera.chat (Nickname regained by services)))
21:40:23*tiorock is now known as rockcavera
21:42:26*tiorock joined #nim
21:42:26*tiorock quit (Changing host)
21:42:26*tiorock joined #nim
21:42:26*rockcavera quit (Killed (erbium.libera.chat (Nickname regained by services)))
21:42:26*tiorock is now known as rockcavera
22:16:52FromDiscord<heysokam> sent a code paste, see https://play.nim-lang.org/#pasty=WFKTjZFi
22:18:12FromDiscord<heysokam> (edit) "https://play.nim-lang.org/#pasty=hwfBdqhk" => "https://play.nim-lang.org/#pasty=gauoMUUb"
22:19:34FromDiscord<hawkey5212> sent a long message, see https://pasty.ee/VUmanuyJ
22:20:36FromDiscord<heysokam> In reply to @hawkey5212 "what's blocking a simple": > what's blocking a simple "you can tell nimble that the dependency is at a given file path"?↵nobody has done it, and nobody wants to work on that codebase for one reason or another↵there is some efforts going on at #tooling for 1.0.0. You could ask there for more details
22:21:16FromDiscord<Elegantbeef> Well we had it with `nimble develop` before they broke that