| 00:04:26 | * | beholders_eye joined #nim |
| 00:08:27 | * | derpydoo quit (Quit: derpydoo) |
| 00:43:52 | * | minimi quit () |
| 01:57:43 | * | beholders_eye quit (Ping timeout: 252 seconds) |
| 04:02:29 | * | andreas quit (Quit: Konversation terminated!) |
| 04:02:40 | * | andreas joined #nim |
| 06:48:26 | * | SchweinDeBurg quit (Quit: WeeChat 4.6.0-dev) |
| 06:53:05 | * | ntat joined #nim |
| 07:02:14 | * | Jjp137 quit (Ping timeout: 260 seconds) |
| 07:02:33 | * | Jjp137 joined #nim |
| 07:46:44 | * | SchweinDeBurg joined #nim |
| 07:52:19 | * | coldfeet joined #nim |
| 07:54:46 | * | ntat quit (Quit: leaving) |
| 08:17:16 | FromDiscord | <nnsee> In reply to @sys64 "I dunno what to": use msvc instead of the default mingw for compiling |
| 08:17:32 | FromDiscord | <nnsee> I've heard that reduces false positives drastically |
| 08:17:54 | FromDiscord | <nnsee> iirc it was `--cc:vcc` |
| 08:36:41 | sh4 | looking into adding nim to my distro, and i peeked at how void linux does it: https://github.com/void-linux/void-packages/blob/master/srcpkgs/nim/template#L16 - they seem to install a lot more than just nim. are all of those bits really needed ? |
| 08:38:51 | sh4 | and if yes, would it make sense to add those bits to an official source release tarball so distros don't have to pick together all the components in matching revisions ? |
| 08:41:42 | FromDiscord | <.tokyovigilante> In reply to @sh4 "and if yes, would": Would be nice 🙂 however once set up it's not too bad. Here's Alpine's draft 2.2 version which I've been chipping in on of late - https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/76837 |
| 08:41:51 | FromDiscord | <.tokyovigilante> (edit) "2.2" => "2.2.2" |
| 08:45:16 | tokyovigilante | ehmry: here's my changes to wayland-scanner for generating interop modules, for interest - https://git.sr.ht/~tokyovigilante/wayland/commit/2efd2c791d70326f86ad84df69e4c86ccc006d68 |
| 08:46:08 | tokyovigilante | Can't imagine it will ever get into an official release, so might be nicer long-term extracted into it's own tool +/- rewritten in nim, given the string handling is pretty painful |
| 08:46:40 | tokyovigilante | working pretty well for me after @ElegantBeef fixed all my bugs :) |
| 08:50:25 | * | minimi joined #nim |
| 09:09:23 | sh4 | elegantbeef is probably the main author ? |
| 09:49:04 | FromDiscord | <System64 ~ Flandre Scarlet> In reply to @nnsee "use msvc instead of": How do I do this...↵If I'm on Linux↵Also, MSVC doesn't have the same levels of optimisations |
| 09:57:49 | * | andreas quit (Quit: Konversation terminated!) |
| 09:58:00 | * | andreas joined #nim |
| 10:30:30 | FromDiscord | <lorenzo.alvarez> sent a code paste, see https://play.nim-lang.org/#pasty=xMquIETr |
| 10:41:58 | * | minimi quit (Ping timeout: 272 seconds) |
| 10:51:35 | FromDiscord | <System64 ~ Flandre Scarlet> I wonder about something↵In Nim, is it possible to await with a timeout?↵And if the timeout is reached, I just give up? |
| 11:22:03 | * | beholders_eye joined #nim |
| 11:34:29 | FromDiscord | <lainlaylie> asyncdispatch and chronos both have withTimeout |
| 11:37:46 | * | ntat joined #nim |
| 11:58:45 | FromDiscord | <nnsee> In reply to @sys64 "How do I do": short answer is VM |
| 12:01:27 | FromDiscord | <nnsee> you're probably able to set up a windows github runner to compile it for you. compiling locally in a VM is probably easier though |
| 12:14:27 | * | ntat quit (Quit: leaving) |
| 12:34:08 | FromDiscord | <System64 ~ Flandre Scarlet> In reply to @nnsee "you're probably able to": I can use Windows LTSC |
| 12:34:23 | FromDiscord | <nnsee> sounds good |
| 12:35:45 | FromDiscord | <nnsee> apparently you can run msvc in wine too https://github.com/mstorsjo/msvc-wine |
| 12:35:49 | FromDiscord | <nnsee> worth a try |
| 12:37:31 | * | ntat joined #nim |
| 12:42:17 | FromDiscord | <System64 ~ Flandre Scarlet> Oh, nice |
| 12:42:48 | FromDiscord | <System64 ~ Flandre Scarlet> In reply to @lainlaylie "asyncdispatch and chronos both": And I guess I can await too? |
| 13:40:30 | FromDiscord | <aintea> sent a code paste, see https://play.nim-lang.org/#pasty=nkxnlghN |
| 13:40:46 | FromDiscord | <aintea> I don't know why Nim would try to call the 'flag' function where it should not |
| 14:45:56 | * | minimi joined #nim |
| 15:26:40 | FromDiscord | <graveflo> this looks odd though. Are you trying to skip over the default parameters with calling `newParser` with two arguments? Also where is the definition of `newParser` that doesn't have the `body` parameter. Are there two other overloads of `newParser`? |
| 15:29:28 | * | coldfeet quit (Quit: Lost terminal) |
| 15:56:21 | * | coldfeet joined #nim |
| 16:35:02 | * | coldfeet quit (Quit: Lost terminal) |
| 17:41:39 | * | minimi left #nim (#nim) |
| 18:08:11 | * | minimi joined #nim |
| 19:52:28 | * | beholders_eye quit (Ping timeout: 268 seconds) |
| 20:38:39 | FromDiscord | <System64 ~ Flandre Scarlet> This is why I need some kind of timeout https://media.discordapp.net/attachments/371759389889003532/1350568903297728542/image.png?ex=67d736ce&is=67d5e54e&hm=e018a7f685ed0a6ac34f7e5589c2005b9b2a6d599b2ed5358c938c138835928c& |
| 20:49:05 | FromDiscord | <Elegantbeef> Need a timeout for what? |
| 20:51:01 | FromDiscord | <System64 ~ Flandre Scarlet> In reply to @Elegantbeef "Need a timeout for": An user can write an infinite loop and crash the entire program, I need to prevent this |
| 21:03:05 | FromDiscord | <Robyn [She/Her]> In reply to @sys64 "How do I do": You could use Zig's bundled clang? |
| 21:03:18 | FromDiscord | <Robyn [She/Her]> They ship the relevant Windows headers and it makes crosscompilation easy |
| 21:07:38 | FromDiscord | <nnsee> In reply to @battery.acid.bubblegum "You could use Zig's": they use mingw |
| 21:07:40 | FromDiscord | <nnsee> afaik |
| 21:07:53 | FromDiscord | <nnsee> which is exactly what i suggested they should prevent |
| 21:09:05 | FromDiscord | <Robyn [She/Her]> In reply to @nnsee "which is exactly what": I remember me and sOkam testing compiling Nim (as an example) with ZigCC rather than whatever the compiler shipped with Nim on windows is, and the binary didn't raise any errors |
| 21:09:12 | FromDiscord | <Robyn [She/Her]> virus warnings |
| 21:10:10 | FromDiscord | <Elegantbeef> Zig? It uses clang |
| 21:10:13 | FromDiscord | <leorize> you can just use llvm.org clang |
| 21:10:14 | FromDiscord | <leorize> it works with msvc runtime |
| 21:10:15 | FromDiscord | <Elegantbeef> Isn't crosscompiling fun with clang? |
| 21:10:15 | FromDiscord | <leorize> tbf the compiler shipped with nim is kinda shady |
| 21:10:25 | FromDiscord | <leorize> I think they ship something better now but it used to be a zip with no known origin |
| 21:10:29 | FromDiscord | <Elegantbeef> We are talking about crosscompiling Leo 😄 |
| 21:10:29 | FromDiscord | <leorize> other than "Araq uses it" |
| 21:10:48 | FromDiscord | <Robyn [She/Her]> In reply to @Elegantbeef "Zig? It uses clang": I know |
| 21:10:51 | FromDiscord | <leorize> I'm following up on robyn latest msg lol |
| 21:10:58 | FromDiscord | <Elegantbeef> Ah |
| 21:11:45 | FromDiscord | <leorize> because nim is really complex. Nightly neovim now have async parsing, so you can use that if you want the delay gone↵(@aintea) |
| 21:11:47 | FromDiscord | <Robyn [She/Her]> In reply to @leorize "you can just use": iirc u gotta install the headers and stuff yourself but that's a really minor thing |
| 21:12:18 | FromDiscord | <leorize> I'd say to just spin windows up and compile instead of cross-compiling \:p |
| 21:12:28 | FromDiscord | <aintea> In reply to @graveflo "this looks odd though.": It's a function that returns a new parser that works perfectly |
| 21:12:36 | FromDiscord | <Robyn [She/Her]> In reply to @leorize "I'd say to just": Could do that too :p |
| 21:12:47 | FromDiscord | <aintea> It is in the context of a library but it is a pain to setup, it's ugly, and a macro would fix this |
| 21:13:01 | FromDiscord | <aintea> In reply to @leorize "because nim is really": That's good to know |
| 21:13:06 | FromDiscord | <aintea> Thank you very much |
| 21:13:47 | FromDiscord | <aintea> (edit) "perfectly" => "perfectly, there is the `newParser` function that returns a new parser, and `newParser` macro, which returns a new parser but takes one more parameter: the body" |
| 21:22:44 | * | beholders_eye joined #nim |
| 21:39:46 | * | ntat quit (Quit: leaving) |
| 22:40:20 | * | andreas quit (Read error: Connection reset by peer) |
| 22:40:21 | * | andreas_ joined #nim |
| 22:47:07 | * | andreas_ quit (Read error: Connection reset by peer) |
| 22:47:14 | * | andreas joined #nim |
| 22:51:41 | * | andreas_ joined #nim |
| 22:51:44 | * | andreas quit (Ping timeout: 244 seconds) |
| 22:55:24 | * | disso-peach joined #nim |
| 22:56:00 | * | andreas_ quit (Ping timeout: 246 seconds) |
| 22:56:03 | * | andreas joined #nim |
| 23:13:51 | * | disso-peach quit (Ping timeout: 246 seconds) |
| 23:22:15 | * | disso-peach joined #nim |
| 23:26:48 | * | andreas quit (Ping timeout: 252 seconds) |
| 23:29:26 | * | andreas joined #nim |
| 23:40:22 | * | andreas_ joined #nim |
| 23:40:22 | * | andreas quit (Read error: Connection reset by peer) |
| 23:51:59 | * | andreas_ quit (Ping timeout: 260 seconds) |
| 23:52:22 | * | andreas_ joined #nim |
