<< 26-09-2025 >>
00:14:04*mal`` joined #nim
01:19:18*Avinash joined #nim
01:31:54*n|Phreak_ quit (Ping timeout: 256 seconds)
01:33:11*Avinash quit (Quit: Have a nice day!)
01:33:26*n|Phreak joined #nim
02:36:30*rockcavera quit (Remote host closed the connection)
02:54:45FromDiscord<sicariusvelox> sent a long message, see https://pasty.ee/KUzXDWCU
02:55:48FromDiscord<sicariusvelox> anyone know of a fix?
03:05:24FromDiscord<sicariusvelox> ill test another terminal later. it might just be the windows terminal as if i pipe the nimble run output to a file via > output.txt i get the output.
03:08:08FromDiscord<janakali> @sicariusvelox it was fixed in latest nimble 0.20.0
03:08:58FromDiscord<sicariusvelox> In reply to @janakali "<@112643965500555264> it was fixed": ooo thanks! i just realised im on 18.2 on my windows machine
03:09:00FromDiscord<janakali> you can update by running `nimble install nimble`
03:09:14FromDiscord<janakali> (edit) "0.20.0" => "0.20.1"
03:11:50FromDiscord<sicariusvelox> thanks!
03:31:46FromDiscord<sicariusvelox> turns out even though i had the latest version installed i had an old .exe version in my .nimble folder that was taking precident.
03:32:03FromDiscord<sicariusvelox> but all fixed now thanks for the help. i can finally see my output 😄
04:54:48*nils` quit (*.net *.split)
05:01:21*nils` joined #nim
05:36:49*LuckyMan joined #nim
05:49:49FromDiscord<systemblue_whale> In reply to @Tóth Alfréd "Unfortunately, the Nim plugin": yes... it's obviously true
05:59:54*nils` quit (Ping timeout: 248 seconds)
06:12:15*nils` joined #nim
06:17:25*nils` quit (Ping timeout: 264 seconds)
06:29:56*nils` joined #nim
07:50:25*nils` quit (Ping timeout: 264 seconds)
08:04:12*nils` joined #nim
08:15:20*LuckyMan quit (Remote host closed the connection)
08:26:25*nils` quit (Ping timeout: 264 seconds)
08:29:13*beholders_eye joined #nim
08:40:02*nils` joined #nim
08:43:36*nils` quit (Read error: Connection reset by peer)
09:01:18*nils` joined #nim
13:22:31*beholders_eye quit (Ping timeout: 240 seconds)
13:33:28*beholders_eye joined #nim
13:40:38*nils` quit (Ping timeout: 256 seconds)
13:47:10FromDiscord<yedco.12> I am using inim, how do I turn on errors that show unhandled exceptions?
13:49:30*phlox left #nim (The Lounge - https://thelounge.chat)
13:55:59FromDiscord<yedco.12> https://media.discordapp.net/attachments/371759389889003532/1421133202960945162/image.png?ex=68d7ecee&is=68d69b6e&hm=b5f16eb6498867269e3ce2e4bed78fc2a76c53037288a35c294046859bd8a970&
15:35:07FromDiscord<yedco.12> I have switched my setup. I'll use a repl, along with that I'll use monit to watch my file
16:23:31FromDiscord<prestosilver> In reply to @janakali "works as well (argh..": I've been meaning to try this for a long while, how is zigs cross comp in nim might use it at some point in the future. Hate mingw so if I have a future project won't be using that for cross
16:23:44FromDiscord<prestosilver> (edit) "nim" => "nim?"
16:29:21FromDiscord<prestosilver> Mostly just curious if it is any consistent between cross comp and local comp, honestly that'd be ideal for my workflow
16:40:42FromDiscord<Robyn [She/Her]> it's pretty good! @heysokam can tell you more too since he's actually used it↵(@prestosilver)
16:55:59FromDiscord<jessatehcrow> how do i properly use `raise`?↵↵whenever i try to use raise to show errors and such it just highlights it in the code here as the error itself, rather than the incorrect place it got used https://media.discordapp.net/attachments/371759389889003532/1421178499540062248/image.png?ex=68d8171e&is=68d6c59e&hm=5ad99acfdb39d2c636acaa2580714fb4aa5bb9c1b5b04d0cce83255e5935e5ca&
17:04:57FromDiscord<prestosilver> I'm pretty sure you can't raise in a macro since it's static execution, someone might have to correct that though. I mostly see calls to this in them instead https://nim-lang.org/docs/macros.html#error%2Cstring%2CNimNode
17:07:03FromDiscord<jessatehcrow> i see
17:07:21FromDiscord<jessatehcrow> unfortunately, that seems to still do the same thing https://media.discordapp.net/attachments/371759389889003532/1421181356733501655/image.png?ex=68d819c7&is=68d6c847&hm=a9a82d7fbdaeef91f2e357dd2ab43727e51e008529706ae56a610ffbbea4975c&
17:08:01FromDiscord<jessatehcrow> which then also doesn't propagate to the actual use of the macro↵↵though, this may be less of a nim problem, and more of a linter one https://media.discordapp.net/attachments/371759389889003532/1421181527601053736/image.png?ex=68d819f0&is=68d6c870&hm=69e7b4cd0505104f2f9cb06db86fb594edd57e54360c6fed9e73ae6f17ac6bc0&
17:08:34FromDiscord<prestosilver> O that's a reraise issue so that could be the case
17:09:23FromDiscord<prestosilver> I had an issue when a macro was erroring at callsite the macro also gets highlighted with lsp, could still be the case
17:10:03FromDiscord<prestosilver> I stopped using lsp a bit back bc my PC couldn't handle the project anymore due to various bad decisions so that could be fixed by now
17:10:25FromDiscord<prestosilver> Does it compile?
17:10:52FromDiscord<prestosilver> (edit) "compile?" => "compile with either?"
17:12:06FromDiscord<prestosilver> Id assume your importing macros too right, probably the case but a good check
17:12:17FromDiscord<jessatehcrow> it compiles, in the sense that it does error expectedly, however, i'm actually seeing a similar issue in the compile logs https://media.discordapp.net/attachments/371759389889003532/1421182599652442265/image.png?ex=68d81af0&is=68d6c970&hm=a873e99db8ec9c643db2c9d2df30750eeb164671e119e08e42ff47b41474c219&
17:12:23FromDiscord<jessatehcrow> In reply to @prestosilver "Id assume your importing": Yes
17:12:45FromDiscord<prestosilver> Oh yea I get it
17:12:53FromDiscord<jessatehcrow> it works as expected for the most part (ie; fails to compile if there's errors) but the actual debug info isn't showing correctly if that makes sense
17:13:36FromDiscord<prestosilver> The underlined is the same issue, since it's a static error lsp is counting it as a normal error, so it gives a full trace at compile time. And lsp counts that as an error
17:13:43FromDiscord<prestosilver> Yea
17:15:07FromDiscord<prestosilver> if you use the n parameter and set it to the node that caused the error then it should raise correctly
17:15:20FromDiscord<jessatehcrow> ahh i see
17:15:38FromDiscord<jessatehcrow> omg, you're right
17:15:50FromDiscord<jessatehcrow> legend
17:16:05FromDiscord<jessatehcrow> thank you !
17:16:15FromDiscord<prestosilver> Bad naming lmao, glad I could help
17:16:29FromDiscord<prestosilver> (edit) "Bad ... namingis" added "parameter" | "parameternaming ... lmao," added "is great"
17:18:48FromDiscord<jessatehcrow> yeah↵looking at my code from 3 years ago, i definitely wasn't great with it myself
17:19:33FromDiscord<prestosilver> https://media.discordapp.net/attachments/371759389889003532/1421184432517415073/20240131_12h51m01s_grim.jpg?ex=68d81ca5&is=68d6cb25&hm=2bc6c94290b83ae9041c859e877821820fe2fbea9d2a58a31544a67d384faafa&
17:19:35FromDiscord<prestosilver> Still beats this
17:19:47FromDiscord<jessatehcrow> oh my
17:21:49FromDiscord<jessatehcrow> at least they're still named
17:22:10FromDiscord<prestosilver> Kinda
17:22:18FromDiscord<jessatehcrow> most of my old stuff was just single letters, none of which were related to what it actually ws
17:22:19FromDiscord<jessatehcrow> (edit) "ws" => "was"
17:22:20FromDiscord<prestosilver> Some of these are actually completely wrong lmao
17:22:37FromDiscord<prestosilver> I fixed this a bit back, glad I did but man
17:22:40FromDiscord<jessatehcrow> ah-↵that may be worse then x33
17:22:41FromDiscord<prestosilver> Sucked to fix
17:22:53FromDiscord<jessatehcrow> i bet
17:30:23FromDiscord<Elegantbeef> @prestosilver
17:30:29FromDiscord<Elegantbeef> Have you considered a struct
17:31:03FromDiscord<prestosilver> That's what I did
17:31:24FromDiscord<Elegantbeef> I only seen the image so was making a joke
17:31:43FromDiscord<prestosilver> I actually used the same params in like 20 other functions, was just a weird design that a struct fixed
17:31:45FromDiscord<prestosilver> So that was only one of the cursed fns
17:31:47FromDiscord<prestosilver> Lmao
17:31:59FromDiscord<Elegantbeef> sent a code paste, see https://play.nim-lang.org/#pasty=kbkMEEVS
17:32:01FromDiscord<prestosilver> That's the worst part
17:32:10FromDiscord<prestosilver> Yea, I used to do globals
17:32:13FromDiscord<prestosilver> That was worse
17:32:33FromDiscord<prestosilver> That was very early on and easy to fix though luckily
17:33:13FromDiscord<prestosilver> Passing the camera is so nice man I wish I did that
17:33:42FromDiscord<prestosilver> My camera has a getter function that takes in my frame ratio and returns it's scale and position, actually abismal
17:34:23FromDiscord<prestosilver> (edit) "My camera has a ... getter" added "annoyingly expensive"
17:35:42FromDiscord<prestosilver> (edit) "abismal" => "abysmal"
17:36:25FromDiscord<prestosilver> Some part of me was like "it'll be smart to process joystick haptics and audio positions through the camera get position function" lmao
18:03:52FromDiscord<Robyn [She/Her]> In reply to @jessatehcrow "unfortunately, that seems to": `error("msg", node)` is what you should do
18:04:04FromDiscord<Robyn [She/Her]> You aren't passing the node for the error to be highlighted on
18:04:49FromDiscord<Robyn [She/Her]> So here, `error("test error", returnType)` is prolly what you want?
18:10:14FromDiscord<mitranim> Playtesting a game where they use loads of random globals for state. It's so full of bugs related to that. Not properly cleaning up between runs or even between rounds forces frequent restarts, except when you restart it loses some states which is not persisted to disk, except it's persisted but ignored when read back, and so on. Take care of your state.
18:16:49*beholders_eye quit (Ping timeout: 264 seconds)
18:44:28*beholders_eye joined #nim
20:01:40FromDiscord<heysokam> In reply to @prestosilver "Mostly just curious if": yes, it is
20:01:47FromDiscord<heysokam> 100% recommend
20:02:08FromDiscord<heysokam> use this: https://github.com/enthus1ast/zigcc
20:09:43*beholders_eye quit (Ping timeout: 240 seconds)
21:19:23*beholders_eye joined #nim
21:19:56*joast quit (Quit: Leaving.)
21:46:13*beholders_eye quit (Ping timeout: 264 seconds)
22:25:24*Jjp137 quit (Quit: Leaving)
22:27:49*Jjp137 joined #nim
22:33:33FromDiscord<nasuray> Or for more pizzaz: https://github.com/daylinmorgan/forge
23:30:22FromDiscord<janakali> In reply to @prestosilver "I've been meaning to": zig cc is just clang with some opinionated defaults (mainly sanitizers are on by default), includes and libs for many targets are packed-in and a few extra features like you can choose a version of libc to compile against.↵↵It works really well for cross-compilation with Nim.
23:38:55*om3ga quit (Ping timeout: 250 seconds)
23:38:55FromDiscord<janakali> sent a long message, see https://pasty.ee/IIfvfsBQ
23:41:18*joast joined #nim
23:46:20FromDiscord<janakali> sent a long message, see https://pasty.ee/tjmbpuMC
23:46:49FromDiscord<janakali> (edit) "https://pasty.ee/ZaurfIxO" => "https://pasty.ee/atELNjCl"
23:52:05FromDiscord<janakali> Oh and clang can hog a lot of RAM at linking in release mode. Adding `--opt:size` nim flag helps if your build environment has low RAM (<= 4GB)