| 01:07:59 | FromDiscord | <janakali> choosenim breaks LSP↵https://github.com/nim-lang/choosenim/issues/13↵alternative: https://forum.nim-lang.org/t/13132↵patch for choosenim: https://forum.nim-lang.org/t/12524 |
| 01:13:26 | FromDiscord | <spotlightkid> The patch has been merged, but it's not in a released version yet, I think. |
| 01:21:57 | FromDiscord | <ringabout> sent a code paste, see https://play.nim-lang.org/#pasty=swaTxehP |
| 01:27:00 | FromDiscord | <janakali> In reply to @odexine "long time no see,": oops, my previous message supposed to be a reply to Rika |
| 01:27:30 | FromDiscord | <odexine> In reply to @janakali "choosenim breaks LSP https://github.com/nim-lang/ch": Oh really, what the heck |
| 01:37:12 | * | xet7 joined #nim |
| 01:38:19 | FromDiscord | <spotlightkid> Yes, araq merged it without taking heed \:-(↵(@ringabout) |
| 01:40:15 | FromDiscord | <spotlightkid> I tried several times to get somebody to help me write proper tests, because I didn't have the time for it and didn't really know |
| 01:40:35 | FromDiscord | <spotlightkid> ... how to write proper tests, because the code doesn't lent itself very well for testing. |
| 01:41:05 | FromDiscord | <spotlightkid> And then, somewhat out of the blue, araq merged it. |
| 01:41:49 | FromDiscord | <spotlightkid> It is probably best to just remove the existing broken test. |
| 01:43:06 | FromDiscord | <ringabout> Yeaah, I agree |
| 01:43:45 | FromDiscord | <ringabout> The error message is clear though |
| 01:47:30 | FromDiscord | <spotlightkid> I have to go to bed now, but I can make a PR fixing or removing the test later today. |
| 01:50:57 | FromDiscord | <ringabout> Thank you! |
| 01:51:58 | FromDiscord | <spotlightkid> To be clear, the failing test was added by my own PR. It wasn't really finished. |
| 01:53:07 | FromDiscord | <spotlightkid> (the test. the changes to proxyexe.nim have been included in the Arch `choosenim` package for months and I never heard of any problem with it.) |
| 01:54:41 | FromDiscord | <ringabout> https://github.com/nim-lang/choosenim/actions/runs/16105649615/job/45440709741 It seems to have some issues building binaries on Windows. Though it could also be pre-existings bugs of choosenim or Nim |
| 01:55:01 | FromDiscord | <ringabout> > [User]\nC:\\Users\\runneradmin\\nimcache\\proxyexe_r\\@mproxyexe.nim.c: In function \'execproxyexe_u10\':\nC:\\Users\\runneradmin\\nimcache\\proxyexe_r\\@mproxyexe.nim.c:650:49: error: passing argument 2 of \'_execv\' from incompatible pointer type [-Wincompatible-pointer-types]\n 650 | T2_ = _execv(nimToCStringConv(path_p0), c_params_1);\n |
| 02:08:44 | FromDiscord | <spotlightkid> Seems like nim passes the `cstringArray` as `char `, but the function expects `const char const`. I'm not sure how one would declare that properly?↵https://github.com/nim-lang/choosenim/blob/69a33921150ba728cbebdf1847f095525ed254af/src/choosenimpkg/proxyexe.nim#L19↵https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/execv-wexecv?view=msvc-170 |
| 02:09:07 | FromDiscord | <spotlightkid> Seems like nim passes the `cstringArray` as `char `, but the function expects `const char const `. I'm not sure how one would declare that properly?↵https://github.com/nim-lang/choosenim/blob/69a33921150ba728cbebdf1847f095525ed254af/src/choosenimpkg/proxyexe.nim#L19↵https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/execv-wexecv?view=msvc-170 |
| 02:23:12 | FromDiscord | <leorize> it doesn't matter |
| 02:24:14 | FromDiscord | <leorize> the const qualifier is a C type-safety feature |
| 02:24:47 | FromDiscord | <leorize> the mistake here is just that they used `{.header.}` for whatever reason |
| 02:34:35 | FromDiscord | <litlighilit> I once met the same issue and get it solved by combining `nim r --eval` `staticRead` and `staticWrite` |
| 02:56:27 | FromDiscord | <litlighilit> sent a code paste, see https://play.nim-lang.org/#pasty=qvhoEMvC |
| 02:57:13 | FromDiscord | <litlighilit> (according to this)↵(@nocturn9x) |
| 03:14:58 | FromDiscord | <litlighilit> sent a code paste, see https://play.nim-lang.org/#pasty=hjhbCiJZ |
| 03:43:17 | * | SchweinDeBurg quit (Quit: WeeChat 4.7.0-dev) |
| 04:07:51 | * | SchweinDeBurg joined #nim |
| 04:14:10 | * | thunder joined #nim |
| 04:47:11 | * | skippy8 joined #nim |
| 05:41:23 | * | xet7 quit (Remote host closed the connection) |
| 05:42:47 | * | xet7 joined #nim |
| 05:47:34 | FromDiscord | <litlighilit> sent a code paste, see https://play.nim-lang.org/#pasty=FixIRsgi |
| 06:06:11 | FromDiscord | <nocturn9x> sent a code paste, see https://play.nim-lang.org/#pasty=YAUFKoeg |
| 06:15:49 | * | xet7 quit (Remote host closed the connection) |
| 06:17:12 | * | xet7 joined #nim |
| 07:21:03 | * | ntat joined #nim |
| 07:24:02 | * | xet7 quit (Remote host closed the connection) |
| 07:26:13 | * | jjido joined #nim |
| 07:32:21 | * | amadaluzia joined #nim |
| 08:18:54 | * | jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…) |
| 08:26:01 | * | beholders_eye joined #nim |
| 08:26:49 | * | nils` quit (Ping timeout: 244 seconds) |
| 09:06:52 | * | nils` joined #nim |
| 09:17:49 | FromDiscord | <morgan (ping with reply)> oh that’s awesome to hear that that choosenim bug is fixed in at least main head |
| 11:18:49 | * | beholders_eye quit (Ping timeout: 260 seconds) |
| 12:44:58 | * | jjido joined #nim |
| 13:03:11 | * | jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…) |
| 13:04:34 | * | nils` quit (Ping timeout: 260 seconds) |
| 13:08:25 | * | beholders_eye joined #nim |
| 13:12:36 | * | skippy8 quit (Ping timeout: 252 seconds) |
| 13:21:30 | * | jjido joined #nim |
| 13:31:07 | * | skippy8 joined #nim |
| 13:35:41 | * | beholders_eye quit (Ping timeout: 252 seconds) |
| 14:18:55 | * | jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…) |
| 14:26:28 | * | ntat quit (Quit: leaving) |
| 14:38:36 | * | ntat joined #nim |
| 15:20:19 | * | jjido joined #nim |
| 15:21:36 | FromDiscord | <TӨMΛ ☠> What does `Error: cannot instantiate: 'T'` mean?↵For context, the part of code it points towards only got one enum added to T generic, so I assume the issue could be that I went with seq using enum? Not sure why would this be an issue though |
| 15:21:44 | FromDiscord | <TӨMΛ ☠> (edit) "enum?" => "enum elsewhere?" |
| 15:36:55 | FromDiscord | <lainlaylie> that error means somewhere the compiler doesn't have enough information to know what T is supposed to be |
| 15:37:17 | FromDiscord | <lainlaylie> (i didn't understand "one enum added to T generic") |
| 15:50:10 | * | jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…) |
| 15:56:59 | * | thunder quit (Ping timeout: 244 seconds) |
| 16:26:07 | FromDiscord | <TӨMΛ ☠> Oh, it's just that I added another enum to this big proc: https://media.discordapp.net/attachments/371759389889003532/1391817567215026216/image.png?ex=686d469e&is=686bf51e&hm=27a868fef4f674b3eca56617fd5a2a99c514f2e964c8fd7712644c0d80ddcc9d& |
| 16:26:38 | FromDiscord | <TӨMΛ ☠> In reply to @lainlaylie "that error means somewhere": Will try to hunt where this issue is, I assumed it's what you say, but then hey, I think everywhere I try to be very explicit? |
| 16:27:05 | FromDiscord | <TӨMΛ ☠> But maybe I missed something, thank you 🙏 |
| 16:32:23 | FromDiscord | <TӨMΛ ☠> Alright, you were right one of the proc calls missed `[]` ^^ |
| 16:34:49 | FromDiscord | <bxiwbbd> In reply to @toma400 "Oh, it's just that": What is up with the indentation |
| 16:34:59 | FromDiscord | <leorize> consider splitting that getEnums proc |
| 16:35:07 | FromDiscord | <leorize> there's really no good reason for it to be generic |
| 17:02:57 | * | jjido joined #nim |
| 17:03:12 | FromDiscord | <Elegantbeef> Didn't even say "consider using parseEnum" 😄 |
| 17:07:42 | FromDiscord | <leorize> they have two strings mapped to one enum so I figured they wanted something custom |
| 17:16:25 | * | ntat quit (Read error: Connection reset by peer) |
| 17:17:09 | * | ntat joined #nim |
| 17:31:57 | * | nils` joined #nim |
| 17:37:00 | * | jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…) |
| 17:39:30 | FromDiscord | <spotlightkid> sent a code paste, see https://play.nim-lang.org/#pasty=ZRWSVxEq |
| 17:40:22 | FromDiscord | <spotlightkid> sent a code paste, see https://play.nim-lang.org/#pasty=BrNxZDkW |
| 17:41:21 | FromDiscord | <Elegantbeef> Probably an issue with the spinner 😄 |
| 17:41:40 | * | xet7 joined #nim |
| 17:43:03 | FromDiscord | <spotlightkid> I was pulling my hair out wondering why the last of three tests in my unit tests didn't seem to be run ( I had a custom `test` task in my nimble file). |
| 17:43:47 | FromDiscord | <spotlightkid> Turn out the test is run, but its output is swallowed. |
| 17:43:56 | FromDiscord | <spotlightkid> Turns out, the test is run, but its output is swallowed. |
| 17:48:50 | * | xet7 quit (Ping timeout: 272 seconds) |
| 17:49:25 | FromDiscord | <spotlightkid> Ah, seems fixed in `nimble@#head` |
| 17:50:57 | FromDiscord | <spotlightkid> And output has no spinner 🙄 |
| 17:53:16 | FromDiscord | <spotlightkid> should have searched the issues\: https://github.com/nim-lang/nimble/issues/1381 |
| 18:00:40 | * | xet7 joined #nim |
| 18:03:00 | FromDiscord | <aintea> is there an easy way to operate with async IO like in netcat ? |
| 18:14:20 | FromDiscord | <Elegantbeef> @aintea Meaning what exactly? |
| 18:20:51 | FromDiscord | <aintea> what ? |
| 18:21:05 | FromDiscord | <aintea> I mean being able to have stdin and stdout "at the same time, non blocking" |
| 18:22:10 | FromDiscord | <aintea> for example run `nc -lvnp 8080` in one terminal and `nc localhost 8080` in another, this is a simple TCP chat, now start typing a message in one room and another in the other room then press enter in one of the sessions, and you'll see the message display even though you were typing a message |
| 18:22:13 | FromDiscord | <aintea> non blocking IO |
| 18:22:24 | FromDiscord | <aintea> I know it is possible to do this with threads but with async ? no idea |
| 18:22:39 | FromDiscord | <Elegantbeef> Don't think you can wrap the stdin and stdout with asyncfile so don't know that you can |
| 18:22:45 | FromDiscord | <aintea> I can |
| 18:22:56 | FromDiscord | <Elegantbeef> Oh that should be doable |
| 18:23:03 | FromDiscord | <aintea> on linux I can just `var stdin_afd = openAsync("/dev/stdin")` |
| 18:23:27 | FromDiscord | <aintea> I have this code for the moment which is somewhat blocking |
| 18:23:35 | FromDiscord | <aintea> sent a code paste, see https://play.nim-lang.org/#pasty=GdMzYcZr |
| 18:23:37 | FromDiscord | <Elegantbeef> I myself avoid async and just use selectors for this |
| 18:23:57 | FromDiscord | <aintea> interesting, I'll take a look at it, thanks |
| 18:24:57 | FromDiscord | <0xfab_10> epoll? |
| 18:25:18 | FromDiscord | <Elegantbeef> I don't overly like the large mechanism and confusion that async brings 😄 |
| 18:26:37 | * | nils` quit (Ping timeout: 265 seconds) |
| 18:28:39 | FromDiscord | <0xfab_10> I really like async |
| 18:30:17 | FromDiscord | <Elegantbeef> You can like it. It's just often more complicated than needed and leaks into the user code |
| 18:30:34 | FromDiscord | <Elegantbeef> I was never one for colouring inbetween lines, so the fact I need to colour procedures sucks |
| 18:33:04 | FromDiscord | <0xfab_10> I like how golang does it |
| 18:34:07 | FromDiscord | <leorize> if only we created something similar in nim |
| 18:34:14 | FromDiscord | <0xfab_10> I don't like the async/await style tho |
| 18:50:48 | * | jjido joined #nim |
| 18:52:31 | FromDiscord | <blackmius> In reply to @leorize "if only we created": i dont know why but every time garbage collector puts a spoke in the weel |
| 18:55:49 | * | Lord_Nightmare quit (Quit: ZNC - http://znc.in) |
| 18:57:58 | * | Lord_Nightmare joined #nim |
| 19:04:55 | * | Lord_Nightmare quit (Quit: ZNC - http://znc.in) |
| 19:07:51 | * | Lord_Nightmare joined #nim |
| 19:09:39 | FromDiscord | <leorize> I'm being sarcastic, we already cooked something with cps |
| 19:16:27 | * | nils` joined #nim |
| 19:24:46 | * | xet7 quit (Remote host closed the connection) |
| 19:27:21 | * | xet7 joined #nim |
| 19:59:11 | FromDiscord | <TӨMΛ ☠> In reply to @bxiwbbd "What is up with": If you mean me using two and one idents loosely it's because I do it on vibes a bit and sometimes it feels better to me to do one and sometimes two (usually things more closely related like 'ofs' get one ident, but there's no strict rule)↵If the spacing to have returns evenly, well, readability is everything for me |
| 20:00:11 | FromDiscord | <TӨMΛ ☠> In reply to @leorize "there's really no good": I could probably split it into 4 overloaded procs, but I kinda find generics as cleaner solution currently |
| 20:01:05 | FromDiscord | <TӨMΛ ☠> It kinda requires me to think of types as I call them |
| 20:03:55 | FromDiscord | <leorize> just know that generics are not type-checked until usage↵(@TӨMΛ ☠) |
| 20:04:08 | * | amadaluzia quit (Quit: ZNC 1.10.0 - https://znc.in) |
| 20:18:29 | FromDiscord | <leorize> In reply to @toma400 "It kinda requires me": I'm not sure what generics do for you here |
| 20:19:37 | FromDiscord | <Elegantbeef> tacusfobe |
| 20:20:04 | FromDiscord | <leorize> there's a lost msg on discord |
| 20:20:22 | FromDiscord | <Elegantbeef> I still like my response |
| 20:25:00 | FromDiscord | <Robyn [She/Her]> In reply to @toma400 "Oh, it's just that": ew |
| 20:27:10 | * | xet7 quit (Ping timeout: 272 seconds) |
| 20:38:55 | * | xet7 joined #nim |
| 20:39:18 | * | skippy8 quit (Ping timeout: 252 seconds) |
| 20:54:40 | * | ntat quit (Quit: leaving) |
| 22:02:09 | * | jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…) |
| 22:29:36 | * | jjido joined #nim |
| 22:30:19 | * | jjido quit (Client Quit) |
| 23:43:54 | * | disso-peach joined #nim |
