<< 30-10-2025 >>
00:02:43*th3r00t quit (Ping timeout: 264 seconds)
00:04:52*th3r00t joined #nim
00:15:17*th3r00t quit (Read error: Connection reset by peer)
00:17:01*th3r00t joined #nim
00:26:53*tiorock joined #nim
00:26:53*tiorock quit (Changing host)
00:26:53*tiorock joined #nim
00:26:53*rockcavera quit (Killed (tungsten.libera.chat (Nickname regained by services)))
00:26:53*tiorock is now known as rockcavera
00:28:12*hygo_ joined #nim
00:31:28*beholder1 joined #nim
00:36:37*hygo quit (*.net *.split)
00:36:37*beholders_eye quit (*.net *.split)
00:36:38*Jjp137 quit (*.net *.split)
00:36:39*cm quit (*.net *.split)
00:36:39*bgupta quit (*.net *.split)
00:42:15*cm joined #nim
00:42:15*bgupta joined #nim
00:42:40*beholder1 quit (Ping timeout: 255 seconds)
01:41:16*rockcavera quit (Remote host closed the connection)
02:02:11*meinside- is now known as meinside
02:41:27*Jjp137 joined #nim
06:27:54*xtr00 quit (Read error: Connection reset by peer)
06:33:50*xtr00 joined #nim
07:23:09FromDiscord<nuitjour_82503> In reply to @Elegantbeef "you either want `ptr": Oddly enough, the implicit de-referencing of using "." or "[i]" does not work, I have to explicitly de-reference with empty square braces, which is advised against in the documentation.↵↵https://play.nim-lang.org/#pasty=lseJXBRY
07:24:18FromDiscord<nuitjour_82503> I feel this use case could be improved upon in the syntax of the language
08:34:19*_th3r00t joined #nim
08:35:29*th3r00t quit (Ping timeout: 256 seconds)
08:45:46FromDiscord<systemblue2010> does really NimConf exists?
08:45:57FromDiscord<systemblue2010> (edit) "exists?" => "exist?"
08:46:16FromDiscord<systemblue2010> when does it be held?
09:14:24FromDiscord<aethrvmn> It has happened in the past, usually in the summer, but mostly digitally
09:17:56FromDiscord<olfactoryhallucinations> There was a NimConf last October, but nothing is planned for this year though. It's been an online-only conference as far as I know.
09:35:12FromDiscord<lainlaylie> In reply to @nuitjour_82503 "Oddly enough, the implicit": it doesn't work for your delete and insert calls because those are ufcs calls, not fields. it does work for index access
10:03:44*beholders_eye joined #nim
10:20:07*beholders_eye quit (Ping timeout: 264 seconds)
10:30:51FromDiscord<tauruuuuuus> In reply to @systemblue2010 "does really NimConf exist?": https://youtube.com/playlist?list=PLxLdEZg8DRwSkT93RIO-CoY-MxHOjYzs2&si=j6GKY-2pJ-hV6_lU↵↵Playlist for the one from last year
11:02:19*beholders_eye joined #nim
11:03:24*Jjp137 quit (Ping timeout: 256 seconds)
11:17:45FromDiscord<nuitjour_82503> In reply to @lainlaylie "it doesn't work for": So the use of empty square brackets is mandatory in that case?
11:19:16FromDiscord<janakali> In reply to @shigumin. "sadly it didn't helped": I believe, zebra and react puzzles were added much later than rest of the puzzles. So many people completed the Nim track without solving those.
11:26:33FromDiscord<janakali> In reply to @shigumin. "sadly it didn't helped": I've had it almost completed for couple years already, just needed a little push to do the React ||(not that hard, but many edge cases)|| and Zebra ||(I gave up after 4 hours of trying and looked up a solution)|| https://media.discordapp.net/attachments/371759389889003532/1433416781552418816/2025-10-30-191619_663x450_scrot.png?ex=69049ce8&is=69034b68&hm=c076d2f29d5b3c0d76dc68a2076cfcabea
11:28:11FromDiscord<janakali> (edit) "couple years" => "more than a year"
11:43:07FromDiscord<lainlaylie> In reply to @nuitjour_82503 "So the use of": afaik
11:44:57FromDiscord<exelotl> today I'm doing crimes https://media.discordapp.net/attachments/371759389889003532/1433421413556945036/image.png?ex=6904a138&is=69034fb8&hm=f40f316dc5c41a3f8ce20c0dd9cbe90fb7b7caba79c65c6540d6803b0d24861c&
12:01:40FromDiscord<heysokam> sent a code paste, see https://play.nim-lang.org/#pasty=olOOeeua
12:08:57FromDiscord<heysokam> Nevermind, I just realized it should be better to create a file for that lang directly from nim at buildtime instead,↵so that it can be imported and used directly as is 🤷‍♂️
12:35:20*vsantana joined #nim
13:11:29*Jjp137 joined #nim
14:31:39FromDiscord<cromlech6677> sent a long message, see https://pasty.ee/QDMeRcDf
14:32:43FromDiscord<cromlech6677> Just a side note, it is a fresh Fedora 43 install, not an upgrade from 42, and I do not have Rust installed in the system
14:33:27FromDiscord<nervecenter> Your build directory has a local rust install
14:33:41FromDiscord<nervecenter> Did you download that example or reproduce it yourself?
14:34:54FromDiscord<cromlech6677> I typed it out from the book into my text text editor and manually compiled with "nim c exercise.nim"
14:35:09FromDiscord<cromlech6677> (edit) removed "text"
14:35:15FromDiscord<nervecenter> sent a code paste, see https://play.nim-lang.org/#pasty=kmYHbxSY
14:35:25FromDiscord<nervecenter> and what does it say
14:35:43FromDiscord<cromlech6677> returns blank line
14:35:56FromDiscord<nervecenter> alright same for me
14:35:59FromDiscord<nervecenter> hmm
14:36:31FromDiscord<nervecenter> type `nim c` and post the output without a file
14:36:44FromDiscord<nervecenter> It should tell you what configs it's using
14:37:39FromDiscord<heysokam> In reply to @cromlech6677 "Hey! Could anyone here": I don't know anything about that library the error mentions↵But the error is saying that `waitLoop` crashed with a `SIGABRT` signal
14:38:21FromDiscord<heysokam> The rust backtrace shows up on signals when something running rust code (even if a library) crashes with a SIG
14:39:05FromDiscord<cromlech6677> sent a code paste, see https://play.nim-lang.org/#pasty=EVNuFFYt
14:39:39FromDiscord<heysokam> `RUST_BACKTRACE=1 ./exercise` should give you more insights on where the abort is being triggered
14:40:05FromDiscord<heysokam> sent a code paste, see https://play.nim-lang.org/#pasty=LbHVsxgR
14:40:25FromDiscord<heysokam> oh wait, nvm. he didn't. misread
14:41:36FromDiscord<heysokam> run your app with the rust backtrace feature active, so see where the error is actually triggered↵It seems to be coming from something beyond nim
14:43:12FromDiscord<cromlech6677> I really don't want to debug Rust at this point. Well, the best solution I found right now is just to roll back to Fedora 42 with my main system, because it works as intended on it... But holy hell, seriously don't understand what went wrong with Fedora 43/Nim/Rust relationship there, almost tearing my hair out. Thanks anyway
14:45:57FromDiscord<heysokam> I'm not asking you to debug rust, I'm asking you to get the backtrace to know where exactly things went wrong↵It might be something misconfigured in Nim, that is triggered on the rust side or something↵But right now we are in the blind
14:46:50FromDiscord<nervecenter> Has Fedora been switching any system libraries to Rust?
14:47:54FromDiscord<cromlech6677> sent a code paste, see https://play.nim-lang.org/#pasty=dgbOvDzG
14:48:00FromDiscord<cromlech6677> sent a code paste, see https://play.nim-lang.org/#pasty=djVWPowE
14:48:37FromDiscord<cromlech6677> In reply to @nervecenter "Has Fedora been switching": that is exactly what I suspect. Currently checking this
14:49:40FromDiscord<nervecenter> Looks like you're calling some graphical libraries there. The `pixels` package seems like a really old thing, trying to research it
14:50:53FromDiscord<nervecenter> Interesting, made by Araq, pulls in SDL
14:50:54FromDiscord<nervecenter> https://github.com/Araq/pixels
14:51:09FromDiscord<nervecenter> Maybe the Fedora SDL version builds some component using Rust
14:51:11FromDiscord<heysokam> In reply to @nervecenter "Looks like you're calling": `you` means `sdl` here↵The crash is triggered by SDL code, deep into their toolchain
14:52:20FromDiscord<heysokam> So it has nothing to do with Nim. Its something wrong either in the SDL bindings or the SDL-rust code in Fedora _(seems like the latter)_
14:52:50FromDiscord<nervecenter> Yup
14:53:26FromDiscord<cromlech6677> would seem so, yeah. Thank you again for your time and effort
14:53:42FromDiscord<heysokam> I would not recommend debugging this↵It seems like some overlook because nobody tested that code in fedora before
14:54:07FromDiscord<cromlech6677> to be honest, Fedora 43 is all kinds of undercooked
14:54:07FromDiscord<heysokam> Try something else that doesn't use SDL, if you are doing this to learn Nim
15:32:00*beholders_eye quit (Ping timeout: 256 seconds)
15:34:44FromDiscord<janakali> In reply to @cromlech6677 "that is exactly what": probably related to the new 'sandboxed image loading framework': https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/desktop/#gdk-pixbuf-glycin↵might be worth it to create an issue: https://gitlab.gnome.org/GNOME/glycin/-/issues
15:47:05FromDiscord<cromlech6677> In reply to @janakali "probably related to the": Thanks! Will look into it.
16:04:20*krunsh joined #nim
16:39:11*beholders_eye joined #nim
19:08:03*lumidify quit (Quit: leaving)
19:09:20*lumidify joined #nim
19:29:43*beholders_eye quit (Ping timeout: 264 seconds)
20:21:19*hygo_ quit (Ping timeout: 264 seconds)
20:23:20*hygo joined #nim
20:45:37*vsantana quit (Ping timeout: 244 seconds)
21:43:25*rockcavera joined #nim
21:54:06*beholders_eye joined #nim
22:21:02*krunsh quit (Read error: Connection reset by peer)
22:43:48*Jjp137 quit (Ping timeout: 256 seconds)
23:00:54*cjaburto joined #nim
23:55:14*_________ quit (Ping timeout: 244 seconds)
23:56:04*_________ joined #nim