<< 24-06-2025 >>

00:07:53*Lord_Nightmare joined #nim
00:17:02*skippy8 quit (Quit: WeeChat 4.6.3)
00:17:48*tokyovigilante quit (Remote host closed the connection)
00:23:49*tokyovigilante joined #nim
02:54:13*tokyovigilante quit (Read error: Connection reset by peer)
02:54:28*tokyovigilante joined #nim
05:18:22FromDiscord<noctis0x1> In reply to @solitudesf "whats your nim version?": 2.0.8
05:32:01FromDiscord<janakali> bruh, that's ancient
05:39:03FromDiscord<noctis0x1> In reply to @janakali "bruh, that's ancient": got it from aur
05:39:14FromDiscord<noctis0x1> guess i will try making from source
05:39:48Amun-Rause the source, Luke (sorry, I couldn't help myself)
05:42:41FromDiscord<janakali> @noctis0x1 You might be interested in grabnim: https://forum.nim-lang.org/t/13132
05:43:53FromDiscord<noctis0x1> In reply to @Amun-Ra "use the source, Luke": the source is with me, updating to 2.2.4 (latest) fixed it
05:44:15Amun-Ra;)
05:44:38FromDiscord<noctis0x1> In reply to @janakali "<@1045279882499850270> You might be": used choosenim as stated in the site
05:46:02FromDiscord<janakali> then please read the forum post above, and then https://github.com/nim-lang/choosenim/issues/13
06:03:35FromDiscord<arnetheduck> sent a code paste, see https://play.nim-lang.org/#pasty=nzmjICxY
06:06:12FromDiscord<arnetheduck> we could still nitpick over whether these really are "one of the following Nim types" due to how importc changes their nature to no longer really make them "nim types" - if I remember it right, in the codegen, some of the integer size promotion rules in the generated C code ends up with slight differences though I don't know that it matters - it would require more extensive investigation of the internals
06:07:11FromDiscord<arnetheduck> good going anyway, we're getting closer to settling this issue
06:09:54*Jjp137 quit (Ping timeout: 276 seconds)
06:10:13*Jjp137 joined #nim
06:11:26*skippy8 joined #nim
06:11:28FromDiscord<arnetheduck> sent a long message, see https://pasty.ee/bDjJInsZ
06:12:59FromDiscord<arnetheduck> in that PR, the rust people rightly have attempted to address this jungle with a slightly more powerful but still well-defined ABI which I can see nim supporting at some point ... so much to do, so little time
06:13:08FromDiscord<arnetheduck> (edit) "in that PR, the rust people rightly have attempted to address this jungle with a slightly more powerful but still well-defined ABI ... which" added "(crabi)"
06:13:30FromDiscord<arnetheduck> (edit) "in that PR, ... the" added "someone mentions"
06:18:09FromDiscord<noctis0x1> In reply to @janakali "then please read the": so i swicthed to grabnim, reinstalled nim using grabnim and the lisp stopped working
06:20:43FromDiscord<janakali> Did you remove all the shims choosenim installs by default?↵You can do it quickly by deleting `~/.choosenim` and `~/.nimble/bin/nim`
06:27:59FromDiscord<noctis0x1> In reply to @janakali "Did you remove all": i kept using an old terminal session , so it didnt recognize the new path 😅
06:28:07FromDiscord<noctis0x1> fixed
06:28:47FromDiscord<noctis0x1> whats a "shim" btw
06:28:52FromDiscord<noctis0x1> (edit) "btw" => "btw?"
06:32:22FromDiscord<janakali> shim/proxy is a thing that provides interface to other thing↵choosenim works by creating fake nim binaries that redirect your input to some other binaries
06:33:22FromDiscord<janakali> @noctis0x1 https://en.wikipedia.org/wiki/Shim_(computing)
06:33:58FromDiscord<noctis0x1> 🫡
07:11:44FromDiscord<lainlaylie> raising awareness of issue 13, love to see it
07:54:31*jjido joined #nim
07:56:02FromDiscord<Phil> In reply to @arnetheduck "I've long wanted to": Reading your very interesting discussion here about C standards I get the distinct impression that how C has basically anything specified is... a mess to say lightly.
07:56:12FromDiscord<Phil> (edit) "lightly." => "lightly.↵For not very much reason too from what I can tell"
07:56:19FromDiscord<Phil> (edit) "In reply to @arnetheduck "I've long wanted to": Reading your very interesting discussion here about C standards I get the distinct impression that how C has basically anything specified is... a mess to say lightly.↵For not very much reason too ... fromat" added "-" | "-from what I can tell ... " added "at least"
07:58:13FromDiscord<leorize> C was created in the era where people haven't figured out how to build computers yet
07:58:37FromDiscord<leorize> so it's defined using an "abstract machine" with very loose rules
07:59:12FromDiscord<leorize> they're tightening it up a bit as of recent standards, though
07:59:18FromDiscord<devlop_gaming> In reply to @leorize "C was created in": How can you create something if you can't figure out how to create the thing needed to create it💀
07:59:27FromDiscord<devlop_gaming> Makes no sense💀
07:59:59FromDiscord<leorize> it's a figure of speech, meaning that the way of the computer is not set in stone
08:00:12FromDiscord<leorize> we had interesting designs like a byte being 7 bits in this period
08:02:04FromDiscord<leorize> but fyi, the first computer program was created long before computer existed
08:05:59FromDiscord<aryzen> Ok so noob question times: I wanna use include to break up a module into multiple files. In this case I have an object I wanna create some procs for. So in the main file for the module I define the object and after that I include the procs file; problem is, the procs file doesn’t seem to see anything from the main file
08:06:18FromDiscord<aryzen> Am I doing it wrong or have I broken something?
08:06:56FromDiscord<leorize> you need to export the symbols you need to access using the `` export marker
08:07:22*jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…)
08:07:35FromDiscord<leorize> see [Export marker](https://nim-lang.org/docs/manual.html#procedures-export-marker)
08:07:43FromDiscord<aryzen> I thought include just flat copied the contents of one file? Exporting is to work with imported modules no?
08:08:04FromDiscord<leorize> oh wait you're using `include`
08:08:13FromDiscord<aryzen> Ya
08:08:16FromDiscord<leorize> have you tried compiling the file?
08:08:43FromDiscord<leorize> if you're using LSP, it's not unlikely for it to connect the graph wrong and not notice that a file is included elsewhere
08:09:42FromDiscord<aryzen> It can compile (I think?? Im having other issues) but nim check seems to flip its shit and nimsuggest kind of flip flops every other input
08:10:07FromDiscord<devlop_gaming> In reply to @leorize "but fyi, the first": How in the fu-💀
08:10:42FromDiscord<aryzen> Unless nim check doesn’t work on the included file directly, cuz it has no issues with the base file
08:10:56FromDiscord<leorize> that's likely the case
08:11:14FromDiscord<aryzen> Oh ok, so pbkac
08:11:44FromDiscord<devlop_gaming> And that's why we don't use nim in the real world🥱
08:12:34FromDiscord<aryzen> I live in a fantasy land in which using swift would lead to issues with console support down the line and nim is the new black
08:13:41FromDiscord<leorize> it's a gamble you take with any niche languages
08:14:11FromDiscord<aryzen> I’ve been having fun fun times with the compiler somehow just flat out accepting my files even though I just filled it with actual keyboard spam so I don’t currently trust it to tell me my program is valid rn XD
08:14:14FromDiscord<devlop_gaming> Realistically any language isn't full of bugs and have plenty of resources 💀
08:14:28FromDiscord<devlop_gaming> In reply to @aryzen "I’ve been having fun": Fair
08:15:20FromDiscord<leorize> i'm jealous, the compiler usually fail with cryptic errors for me
08:16:59FromDiscord<devlop_gaming> Who wrote this compiler💀
08:17:57FromDiscord<leorize> he's active in #internals if you wanna complain
08:18:38FromDiscord<aryzen> Of course if I run nim check suddenly the compiler realizes it’s not actually valid nim so idk it’s 3am and I’m probably doing something really stupid
08:18:54FromDiscord<leorize> when in doubt, blame all editor integrations
08:19:06FromDiscord<aryzen> Yeah, I can’t wait for nim3
08:19:34FromDiscord<aryzen> Hopefully the overhaul brings more stable tools
08:20:52FromDiscord<leorize> \cough\ IC \cough\
08:28:28FromDiscord<devlop_gaming> In reply to @leorize "he's active in #internals": Who is he?
08:28:58FromDiscord<devlop_gaming> In reply to @aryzen "Hopefully the overhaul brings": And more tools
08:33:36FromDiscord<leorize> Araq
08:34:41FromDiscord<aryzen> I want two things. Obviously they aren’t small things though. One is stable LSP, and the other is debugging symbols that line up with the actual code
08:35:01FromDiscord<aryzen> (edit) "code" => "code/better debugging in general"
08:39:18*beholders_eye joined #nim
08:51:33FromDiscord<devlop_gaming> Forget all that when we getting packages that people are actually gonna maintain 💀
08:54:31FromDiscord<aryzen> In reply to @devlop_gaming "Forget all that when": https://discord.com/channels/371759389889003530/371759389889003532/1386982601570517013
08:55:04FromDiscord<devlop_gaming> In reply to @aryzen "https://discord.com/channels/371759389889003530/371": And that means what exactly?
08:56:08FromDiscord<aryzen> “It’s a gamble you take with niche languages”; was a joke
08:59:02FromDiscord<devlop_gaming> Oh?
09:04:05*skippy8 quit (Quit: WeeChat 4.6.3)
09:08:26*skippy8 joined #nim
09:12:06*skippy8 quit (Client Quit)
09:46:19FromDiscord<Phil> In reply to @leorize "C was created in": Curse this historical tech debt
10:03:26*xet7 joined #nim
10:03:47*xet7 quit (Remote host closed the connection)
11:41:56FromDiscord<arkanoid> which RPC library for nim 2.2.4 and beyond?
11:43:03FromDiscord<arkanoid> I wish this screen would display some stats (from github?) to find which library is alive or not https://nimble.directory/search?query=rpc
12:08:46FromDiscord<spotlightkid> arkanoid\: https://nimpkgs.dayl.in/?query=rpc#/search shows the last commit for each project.↵I always use this site instead of nimble.directory
13:05:32*skippy8 joined #nim
13:20:32*rockcavera quit (Remote host closed the connection)
13:20:50FromDiscord<nasuray> I've been meaning to improve the filtering toggles but haven't gotten around to it yet. But currently you can sort by recent commits or recently tagged versions
14:00:30FromDiscord<arkanoid> spotlightkid\: thanks!
14:01:26FromDiscord<arkanoid> mh, no nimble in official nim docker images? just pulled nimlang/nim\:2.2.4-alpine-slim and no nimble in it
14:02:24FromDiscord<arkanoid> oh! wait\: Slim images include only the Nim compiler. Regular images include the compiler and Nimble⁠ package manager.
17:05:58*rockcavera joined #nim
17:22:05*jjido joined #nim
17:22:49*jjido quit (Client Quit)
17:23:26*skippy8 quit (Quit: WeeChat 4.6.3)
17:42:04FromDiscord<aryzen> sent a code paste, see https://play.nim-lang.org/#pasty=bNWVEQug
17:45:48Amun-Rathat's how you write setters
17:47:46FromDiscord<aryzen> awesome! the backtick requirement is annoying though lol
17:48:34Amun-Rayou'll get used to it :P
17:48:58Amun-Rait's needed to escape the special character =
18:27:36*jjido joined #nim
18:50:57FromDiscord<arkanoid> I feel stupid, could you please explain me where are the the dockerfiles for the ubuntu variant here? https://github.com/nim-lang/docker-images/tree/develop
19:42:15*jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…)
20:03:31*jjido joined #nim
20:08:28*jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…)
20:17:39*Ekho quit (Ping timeout: 260 seconds)
20:25:51FromDiscord<spotlightkid> arkanoid\: I believe the images are actually built using this tool\: https://github.com/moigagoo/dhbp
20:26:16FromDiscord<spotlightkid> See also\: https://github.com/nim-lang-ci/docker-images-regular
20:29:28FromDiscord<arkanoid> thank, but still don't get where it picks which version of ubuntu parent image
20:29:36*Ekho joined #nim
20:49:21*beholders_eye quit (Ping timeout: 276 seconds)
21:04:38FromDiscord<spotlightkid> This workflow uses dhpb to build the images\: https://github.com/nim-lang-ci/docker-images-regular/blob/develop/.github/workflows/22x.yml↵dhbp has its own config and Dockerfile templates
21:08:45FromDiscord<spotlightkid> But, I admit, I don't fully understand the details as well.
21:13:53*rockcavera quit (Ping timeout: 248 seconds)
21:14:39FromDiscord<arkanoid> all I know is that "nimlang/nim\:2.2.4-ubuntu-regular" is built on Ubuntu 20.04.6 LTS, which reached EOL May 2025 https://ubuntu.com/about/release-cycle
21:15:05FromDiscord<arkanoid> not sure if it is intended or not, I think not, because I can't read "20.04" anywhere, but I read some "latest"
21:15:15FromDiscord<arkanoid> which make me think that there's an issue somewhere
21:47:32*SchweinDeBurg quit (Read error: Connection reset by peer)
21:47:51*SchweinDeBurg joined #nim
22:24:56*rockcavera joined #nim
23:15:36*perro quit (Ping timeout: 276 seconds)
23:47:09FromDiscord<gokr> Before dropping to bed, vibe coded 🙂 an MCP library to make MCP servers. I use Claude Code (paid for the Pro subscription which goes a long way for hobby hacking) and ... it is a super fun and capable tool: https://github.com/gokr/nimcp
23:48:48FromDiscord<gokr> I admit I haven't tested all bits of it - but it does work inside Claude Code itself - both spawned and used via stdin/stdout and using http.
23:48:59FromDiscord<0xfab_10> do we have the new nim yet I'm a bit out of touch