<< 16-01-2025 >>

00:00:58FromDiscord<Robyn [She/Her]> In reply to @michaelb.eth "note that casting seq[uint8]": Strings and seqs are different
00:01:25FromDiscord<Robyn [She/Her]> Strings are currently laid out in the same way as a seq except for the null terminator included for costless C interop
00:36:01FromDiscord<michaelb.eth> right, I meant that the cast to string isn’t the best approach even if the last byte in the seq is null terminator, but maybe it’s okay in that situation
01:56:35FromDiscord<System64 ~ Flandre Scarlet> It's a bit noisy here! https://media.discordapp.net/attachments/371759389889003532/1329268030340988949/image.png?ex=6789b8d3&is=67886753&hm=5c19dcbb71afe62f9b2b77f34574187e63c4c369536f9e33c48fc94832e09f51&
02:07:04FromDiscord<odexine> what? i cant hear you
02:12:09FromDiscord<System64 ~ Flandre Scarlet> In reply to @odexine "what? i cant hear": Lol↵It's a joke because I made a noise module
02:12:33FromDiscord<odexine> i mean yeah i also played into the joke what
03:06:57*xet7 quit (Remote host closed the connection)
03:33:11*krux02 quit (Remote host closed the connection)
04:12:21*m5zs7k quit (Ping timeout: 276 seconds)
04:17:09*m5zs7k joined #nim
04:47:35*SchweinDeBurg quit (Quit: WeeChat 4.6.0-dev)
04:47:59*SchweinDeBurg joined #nim
05:35:40FromDiscord<xtrayambak> In reply to @sys64 "It's a bit noisy": Is that IMGui?
07:11:12*attah quit (Ping timeout: 244 seconds)
07:12:19*attah joined #nim
07:16:39FromDiscord<System64 ~ Flandre Scarlet> In reply to @xtrayambak "Is that IMGui?": Yes!
08:14:28*attah_ joined #nim
08:14:48*attah quit (Ping timeout: 276 seconds)
08:15:05*attah_ is now known as attah
09:30:21*alexdaguy joined #nim
11:18:49FromDiscord<albassort> is there a way to reset an http client so it doesn't hang like its been doing for the past 5 years?
11:22:56*beholders_eye joined #nim
11:33:54Amun-Ratimeout?
11:37:48FromDiscord<albassort> In reply to @Amun-Ra "timeout?": has never worked historically for me
11:37:57FromDiscord<albassort> its something low level
11:40:18Amun-Rahmm
11:45:26FromDiscord<albassort> i could use puppy here
12:47:00*disso-peach joined #nim
13:05:04FromDiscord<melmass> What are the alternatives to nimble? ↵I still get some weird lock issues (running nimble lock consecutively produce different lock files, hence `nimble develop` works half of the time)
13:21:20*m5zs7k quit (Ping timeout: 265 seconds)
13:21:48FromDiscord<pmunch> Not the best name for getting `@`ed..
13:35:09*m5zs7k joined #nim
13:43:06FromDiscord<janakali> @melmass atlas, git submodules, nix
13:45:28FromDiscord<melmass> In reply to @janakali "<@499629400254447616> atlas, git": I forgot about atlas thanks I meant to look into it, it seemed a bit much for my needs, but nimble is causing me many issues, I initially thought they were windows related but I experience the same issues on mac (cache can get corrupted, lock issues I mentionned earlier, the weird way it updates nim itself)
13:45:55FromDiscord<melmass> (edit) "updates" => "can update"
13:53:51*alexdaguy quit (Quit: w)
14:33:48FromDiscord<xtrayambak> sent a code paste, see https://play.nim-lang.org/#pasty=IqWBEbUo
14:38:21Amun-Raonly via `const C = A`
14:47:48FromDiscord<xtrayambak> Thanks
14:50:54FromDiscord<xtrayambak> In reply to @albassort "i could use puppy": Just use curly, it works well
14:51:26FromDiscord<xtrayambak> you get the added benefit of using libcurl and you can rest assured it can handle 99% of cases
15:21:20*kotrcka joined #nim
15:51:22*kotrcka quit (Remote host closed the connection)
15:59:30FromDiscord<jmgomez> In reply to @melmass "What are the alternatives": > nimble lock consecutively produce different lock files↵I found, and ship a fix for it, today. ↵Next time you find something odd, please fill an issue so it can be fixed
16:00:05FromDiscord<jmgomez> Here is the PR https://github.com/nim-lang/nimble/pull/1334 (it may take a day or two to be merged)
16:00:07*termer quit (Quit: ZNC 1.8.2+deb2ubuntu0.1 - https://znc.in)
16:00:32FromDiscord<melmass> In reply to @jmgomez "> nimble lock consecutively": Thanks Juan! ↵I wasn't sure if it was a me error and did not investigate further
16:00:45FromDiscord<melmass> (I also thought nimble wasn't being worked on much, I was wrong)
16:01:38FromDiscord<jmgomez> Np. But yeah, its the first priority for the time being in the tooling front
16:02:46FromDiscord<melmass> Btw the LSP works much better than a few months back for me in neovim (no crashes, I sometime have to restart it to catchup but not more than any other lsp)
16:03:30FromDiscord<tauruuuuuus> Yup same for me on vscode/helix, the experience is much better 😛
16:04:17FromDiscord<jmgomez> Thats great to hear 🙂
16:48:41*beholders_eye quit (Ping timeout: 265 seconds)
16:51:20FromDiscord<threefour> In reply to @melmass "I forgot about atlas": What is the state of Atlas? I used it a bit probably half a year ago, but got the impression that it lacks polish and is kind of neglected. Is this the case? Has it changed? Is it supposed to faze out Nimble entirely, or just be an alternative for the foreseeable future?
16:51:31FromDiscord<linuxlefty> I'm trying to sign up for the Nim forum, but when I create an account it errors with `Couldn't send email`. Any idea how to fix this?↵↵@pmunch I was told to tag you 🙂
16:53:08FromDiscord<threefour> Nvm answered my own question
16:53:49*disso-peach quit (Quit: Leaving)
16:54:07FromDiscord<melmass> Pretty much my experience (around the same time as well) but Araq keep recommending it. I'm not sure it's 100% comparable to nimble, it feels more like what uv does for python (runtime (nim installs), env and package managment) I guess some aspects do converge but atlas feels like it has a larger scope
16:54:17FromDiscord<melmass> @threefour 👆
16:54:21FromDiscord<pmunch> In reply to @linuxlefty "I'm trying to sign": Just PM me the nickname and email address you want and I'll get an account set up for you 🙂
16:58:17FromDiscord<threefour> In reply to @melmass "Pretty much my experience": Yeah either I didn't pay attention to the README & description on GitHub last time I used it, or it was updated since, because I visited it and now it seems pretty obvious it's supposed to be like uv. Or maybe like Python virtual environments even.
17:59:48*SchweinDeBurg quit (Ping timeout: 276 seconds)
18:23:31*SchweinDeBurg joined #nim
18:32:44FromDiscord<michaelb.eth> is dimscord the way to go for Nim bot these days, or someone's fork, or something else that maybe isn't in nimble.directory?
19:27:31*ntat joined #nim
19:38:25FromDiscord<albassort> can i compile a nim file to a js module and call it from js
19:38:32FromDiscord<albassort> ive inthe past has to manually modify the files
19:38:38FromDiscord<albassort> to make an entry point
19:48:44FromDiscord<albassort> {.exportc.} works like it does in a clib
19:48:46FromDiscord<albassort> lole
19:55:38*coldfeet joined #nim
20:03:20FromDiscord<nasuray> you can always utilize the `emit` pragma if it isn't natively producing what's necessary for javascript to import the module.
20:14:09*coldfeet quit (Ping timeout: 246 seconds)
20:15:54*coldfeet joined #nim
20:26:21*coldfeet quit (Ping timeout: 244 seconds)
20:37:19*ntat quit (Quit: Leaving)
20:46:27FromDiscord<starkiller1493> Has anyone had a similiar problem? I'm having trouble with VSCode using nimlangserver (all latest stable) not seeing installed packages when `nimble c` can see them.
20:47:48*coldfeet joined #nim
20:56:09*coldfeet quit (Ping timeout: 265 seconds)
20:57:28FromDiscord<mjsdev> I had to generate the .paths file?
20:57:50FromDiscord<mjsdev> Coming from PHP... the package/nimble experience compared to composer is pretty bad
20:58:33FromDiscord<mjsdev> With respect to my meta programming dreams for my dynamic application framework... I think I'm ultimately hitting a wall
21:02:25*krux02 joined #nim
21:02:55FromDiscord<starkiller1493> Oh, that's new
21:03:02FromDiscord<starkiller1493> thanks
21:07:33FromDiscord<mjsdev> It seems to be using `nim` directly in some sense behind the scenes... and nim alone doesn't seem to know about the include paths otherwise from normal nimble setup.
21:07:39*coldfeet joined #nim
21:07:57FromDiscord<mjsdev> You can test by trying to compile the project with `nim` directly -- if it doesn't work, chances are your vscode/langserver stuff won't work right.
21:09:59FromDiscord<starkiller1493> nimble setup fixed it
21:19:52*coldfeet quit (Ping timeout: 252 seconds)
21:20:20FromDiscord<Robyn [She/Her]> In reply to @Amun-Ra "only via `const C": Not really
21:25:42FromDiscord<Robyn [She/Her]> actually nvm
21:25:51FromDiscord<Robyn [She/Her]> was tryna do something with templates but pain
21:26:29FromDiscord<Elegantbeef> `proc C(_: typedesc[MyEnum]): MyEnum = A`
21:26:31FromDiscord<Elegantbeef> No need for anything complex
21:27:34FromDiscord<Robyn [She/Her]> In reply to @Elegantbeef "`proc C*(_: typedesc[MyEnum]): MyEnum": I was trying to make an `enumAlias` templaete that generated that + one without the enum type
21:28:02FromDiscord<Elegantbeef> So you just did \`enunAlias C, A?
21:30:53*coldfeet joined #nim
21:31:38FromDiscord<Elegantbeef> QED
21:31:38FromDiscord<Elegantbeef> sent a code paste, see https://play.nim-lang.org/#pasty=ZUceuAGl
21:36:02*coldfeet quit (Remote host closed the connection)
21:36:28*coldfeet joined #nim
21:36:28*coldfeet quit (Changing host)
21:36:28*coldfeet joined #nim
21:38:19FromDiscord<mjsdev> What's up with `_` by the way?
21:39:01FromDiscord<Elegantbeef> unused symbol
21:39:01FromDiscord<mjsdev> That makes it unusable in the procedure (so far as I can tell?)
21:39:41FromDiscord<mjsdev> Right, but why not call it `self` or something? so you could call other static procs or get other info... it seems like a weird habit/convention.
21:40:27FromDiscord<Elegantbeef> Cause we don't need it and naming variables self is stupid
21:41:09FromDiscord<Elegantbeef> Nim is not OOP there is not attachment to an instance
21:41:21FromDiscord<Elegantbeef> So using `this` or `self` is a pointless endeavour attempting to pretend they're type attached operations
21:42:04FromDiscord<mjsdev> Seems as valid a convention as any. Whether or not you need it kinda depend on the proc body
21:42:28FromDiscord<Elegantbeef> Right, and if you use `_` you know you didn't need it
21:42:42FromDiscord<Elegantbeef> Cause if you did need it you cannot access it as `_` is a special symbol
21:44:02*rockcavera joined #nim
21:46:39*coldfeet quit (Ping timeout: 276 seconds)
21:52:31*coldfeet joined #nim
21:59:29*coldfeet quit (Ping timeout: 260 seconds)
22:07:05FromDiscord<Robyn [She/Her]> Time to figure out a way to try and iterate through all control flow structures
23:24:29*rockcavera quit (Remote host closed the connection)
23:28:52*rockcavera joined #nim
23:37:37FromDiscord<albassort> how many socket connections can i have open?
23:37:56FromDiscord<albassort> my dispatcher takes in a connection to a socket, then sends it over to a thread
23:37:57FromDiscord<Elegantbeef> OS file limit
23:38:01FromDiscord<albassort> ic
23:38:38FromDiscord<albassort> so i assume when i have a socket and send it off, the file descriptor is transferred to the other process
23:39:29FromDiscord<Elegantbeef> Sockets are ref objects so you'd have to do `wasMoved(sock)` after sending them to be certain
23:39:42FromDiscord<Elegantbeef> Though you could pass just the FD then remake the socket if possible
23:40:13FromDiscord<Elegantbeef> Or send a `SocketImpl` instead
23:41:05FromDiscord<albassort> yeah the FD has to move because i overwrite it on the next loop.
23:41:11FromDiscord<albassort> i must raise the fd limit
23:46:43FromDiscord<Elegantbeef> I'm just imagining you like Oliver Twist asking for more FDs