<< 12-10-2024 >>
00:05:53FromDiscord<eightbit_dboy> In reply to @eightbit_dboy "I'm getting this error": So anything I can do about this error?
00:06:11FromDiscord<eightbit_dboy> I had managed to get Nim to compile for the N64 before without issue.
00:06:31FromDiscord<eightbit_dboy> I guess maybe it's down to futhark using the `os` module?
00:06:39*krux02 joined #nim
00:08:29FromDiscord<eightbit_dboy> Yeah, so I gotta get it to not do this: https://media.discordapp.net/attachments/371759389889003532/1294451589528031293/image.png?ex=670b0f7c&is=6709bdfc&hm=d9cc6235a794d521dab735d24e8da413a7e8e3cd596af01faf704b5c48399aa6&
00:16:11FromDiscord<eightbit_dboy> Commented that out and it's giving me this error, now: https://media.discordapp.net/attachments/371759389889003532/1294453526549758003/image.png?ex=670b114a&is=6709bfca&hm=3de75a4a39078e76735a9cf392344ba6bbc975d2dab0c32d3ab011baa0e0a0ee&
00:16:27FromDiscord<eightbit_dboy> Not sure why, sinceinitWindow is in naylib64.
03:19:05*SchweinDeBurg quit (Quit: WeeChat 4.5.0-dev)
03:19:30*SchweinDeBurg joined #nim
03:54:38*krux02 quit (Remote host closed the connection)
05:21:03*Batzy_ joined #nim
05:23:40*Batzy quit (Ping timeout: 252 seconds)
05:25:36*Batzy joined #nim
05:28:21*Batzy_ quit (Ping timeout: 248 seconds)
05:29:57*Batzy quit (Ping timeout: 248 seconds)
06:12:25*Batzy joined #nim
06:21:15*jkl quit (Quit: Gone.)
06:24:26*jkl joined #nim
06:24:58*bcksl quit (Quit: \)
06:24:58*end quit (Quit: end)
06:37:29*bcksl joined #nim
06:42:40*end joined #nim
06:50:05*coldfeet joined #nim
06:56:58FromDiscord<xkonti> There's no showcase channel so I'm gonna throw it in here. If somebody is looking for something to do for Hacktoberfest, look no further 🙃 https://github.com/Xkonti/surrealdb.nim
07:03:07FromDiscord<Elegantbeef> Need more `sink`
07:05:03FromDiscord<Elegantbeef> At a cursory look the `nextId` likely should be thread local in case someone is running this on multiple threads for whatever reason
07:05:54FromDiscord<Elegantbeef> Or it should be an atomic int
07:06:07FromDiscord<Elegantbeef> That's what it should be 😄
07:16:08*coldfeet quit (Quit: leaving)
07:28:15*ntat joined #nim
07:45:43FromDiscord<xkonti> In reply to @Elegantbeef "That's what it should": Thanks for the recommendations 😄
07:57:08*tokyovigilante joined #nim
08:06:31FromDiscord<xkonti> In reply to @Elegantbeef "That's what it should": I think you might have looked at the main branch. The `cbor` branch is the current development branch and would probably give you a proper headache 😂
08:29:42tokyovigilanteHi, I'm using (or hoping to) use Nim on Alpine Linux, which uses musl libc. There are a couple of issues around pthread_t types and 32/64-bit time_t definitions which can be patched in the downstream distro packages, and I see there are some defines for specific distros, but is there any appetite for adding libc detection to nim's buildsystem?
08:45:17*coldfeet joined #nim
09:32:39FromDiscord<eilerolrikpottestepper> sent a code paste, see https://play.nim-lang.org/#pasty=AQJIISal
09:33:27FromDiscord<solitudesf> In reply to @eilerolrikpottestepper "Hi, I am trying": you need to install mingw and use `-d:mingw` switch
09:34:00FromDiscord<eilerolrikpottestepper> sent a code paste, see https://paste.rs/lCed2
09:34:25FromDiscord<eilerolrikpottestepper> Isn't mingw for windows?
09:35:14FromDiscord<odexine> It’s for compiling to windows
09:37:50FromDiscord<eilerolrikpottestepper> Ahh ok. Using mingw I get even more errors The full output is: https://pastebin.com/nrzVuHcV
09:56:25FromDiscord<jmgomez> In reply to @xkonti "There's no showcase channel": Great work, you may want to do a forum post as well
09:57:35FromDiscord<_elbie_> In reply to @eilerolrikpottestepper "Hi, I am trying": Also need the windows api headers, not just the mingw compiler. On debian-likes (debian, devuan, ubuntu, mint, etc.), I think the mingw-w64-x86-64-dev package is what you would need. Installing apt-file and doing apt-file update && apt-file search windows.h should confirm.
10:09:18*beholders_eye joined #nim
10:10:32FromDiscord<griffith1deadly> In reply to @eilerolrikpottestepper "Isn't mingw for windows?": use it without --os
10:10:52FromDiscord<griffith1deadly> as i tested simply -d mingw -cpu:amd64 worked fine
10:22:20*beholders_eye quit (Quit: WeeChat 4.1.2)
10:49:14*ryuukk quit (Remote host closed the connection)
10:51:49*coldfeet quit (Remote host closed the connection)
10:55:39*ryuukk joined #nim
11:11:04FromDiscord<eilerolrikpottestepper> Thanks! I got it working
11:32:10FromDiscord<you33me=> So what do I learn here\`
13:13:02*ntat quit (Quit: Leaving)
13:16:25FromDiscord<majortrips1763> :w
13:20:45FromDiscord<majortrips1763> sent a code paste, see https://play.nim-lang.org/#pasty=JiUzvmvk
13:23:13FromDiscord<xkonti> In reply to @jmgomez "Great work, you may": Thank you. Will do 🙂
13:29:20*ntat joined #nim
13:30:09*ryuukk quit (Remote host closed the connection)
13:32:58*ryuukk joined #nim
13:42:55*coldfeet joined #nim
14:24:27FromDiscord<jmgomez> In reply to @xkonti "Thank you. Will do": also consider adding it to here: https://github.com/ringabout/awesome-nim
14:29:06FromDiscord<xkonti> In reply to @jmgomez "also consider adding it": After CBOR is fully implemented 🙂
14:37:55FromDiscord<majortrips1763> Oh, interesting .. found a bug in `nim doc` I think
14:42:18FromDiscord<majortrips1763> So weird, escaping a `field` name results in it being hidden from the docs?
14:42:55FromDiscord<jmgomez> In reply to @xkonti "After CBOR is fully": Okay, but its good to advertise it so maybe you get some help from others interested. BTW how are your experiments with NUE going? Im about to start the project for the NimConf, likely will be talking about different kind of bindings that I think not many people knows about
14:43:49FromDiscord<odexine> In reply to @majortrips1763 "So weird, escaping a": “Escaping”?
14:44:18FromDiscord<majortrips1763> type Foo: object↵ `param`: uint32
14:44:26FromDiscord<majortrips1763> (edit) "type Foo: object↵ `param`: uint32" => "sent a code paste, see https://play.nim-lang.org/#pasty=uKbhuTIk"
14:44:29FromDiscord<odexine> Oh stropping
14:44:37FromDiscord<odexine> Seems strange
14:45:26FromDiscord<majortrips1763> Some of the field names I was using are keywords in Nim .. I was trying to reference the original spec as close as possible, but in doing so those fields are ejected from the output of `nim doc`
14:51:23FromDiscord<majortrips1763> Hmm, doc local references don't work for types? only proc/const/iterator?
14:52:16FromDiscord<xkonti> In reply to @jmgomez "Okay, but its good": I'm on pause with NUE at the moment as I feel like I need to get to know Nim itself a bit better and Unreal itself as well. Although I will probably end up using NUE for procedural generation with wave function collapse 😄
14:57:14FromDiscord<jmgomez> In reply to @xkonti "I'm on pause with": Makes sense. UE is kinda of daunting at the beginning and of course adding Nim on top doesnt make it any simpler especially for the advance features. For procedural content generation, PCG is great, it has a houdini like approach. Pretty sure you can implement WFC on top of it and it will ease things out. In my experiments with PCG (when it was experimental) I was able to make nodes in Nim with l
15:09:35FromDiscord<xkonti> sent a long message, see https://pasty.ee/PtyvQmai
15:17:49FromDiscord<Nelson> Hello everyone! I'm super new to Nim and giving it another chance↵↵I am having a specific design issue in regards to accessing (global?) tables from threads, my code editor would always say something about not being able to use a GC'd variable from a thread
15:18:43FromDiscord<Nelson> I think it's better if I explain what I want to do\: essentially I want an asset cacher, a function that when passed a filename, it would return a placeholder until it can return me the actual file i'm requesting after having offloaded the work to another thread
15:20:09FromDiscord<Nelson> perhaps add some pointer to some enum to the function signature so i can figure out also in what state is the current asset, for example\: Ready, Loading, Failed↵↵all of this being cached onto some map which is meant to be cleaned out by another function after something goes unused for too long
15:23:44*disso-peach joined #nim
15:44:59FromDiscord<Nelson> Maybe I could use Channels?
15:46:59FromDiscord<spotlightkid> Probably yes.
15:47:38FromDiscord<Nelson> Yeah I didn't know they were a thing here in the std lol
15:47:45FromDiscord<spotlightkid> https://github.com/nim-lang/threading
15:47:52FromDiscord<grumblygibson> In reply to @Nelson "Maybe I could use": You can also check out stashtables to see if they help (tables for threaded situations)
15:48:01FromDiscord<Nelson> oooooo
16:09:51*disso-peach quit (Quit: Leaving)
16:16:26FromDiscord<spotlightkid> Does dynamic library loading via the `dynlib` pragma use the `LD_LIBRARY_PATH` env variable? Also on macOS?
16:39:18FromDiscord<sOkam! 🫐> What could be the equivalent to packed structs in Nim?
17:24:11Amun-Raspotlightkid: iirc LD_LIBRARY_PATH is DYLD_LIBRARY_PATH on macos, and it should work with dynlib
18:07:28FromDiscord<majortrips1763> Any idea on how to create a local reference in the docs to link to an object?
18:11:03*coldfeet quit (Remote host closed the connection)
18:43:40strogon14_Amun-Ra: according to the dlopen man page both are used.
18:44:22strogon14_But my problem probably has to do with an incompatible library, not with dynlib not finding it.
18:44:40Amun-Rastrogon14_: I wasn't sure whether LD_* works, I don't own post-ppc mac
18:45:35strogon14_Me neither. But I'm trying to get a GH actions workflow to work where I install a library on macOS using brew
18:50:22strogon14_So far no luck. But I have to work now, will try again tomorra
19:09:25FromDiscord<frusadev> Hey! There's something i don't quite understand... What are ref objects?
19:18:23FromDiscord<Elegantbeef> Heap allocated reference types that are automatically managed
19:24:52FromDiscord<majortrips1763> Soo .. no no love on docgen for object references? I was sort of hoping I was just doing something wrong.
19:27:57FromDiscord<Elegantbeef> https://nim-lang.org/docs/docgen.html#simple-documentation-links-nim-local-referencing
19:28:02FromDiscord<Elegantbeef> There is a reference on how it's done for objects
19:35:41FromDiscord<majortrips1763> I must be missing something... the syntax I am using works for proc and enum, but not objects.
19:51:43FromDiscord<double_spiral> sent a code paste, see https://play.nim-lang.org/#pasty=OctgexPg
19:54:14FromDiscord<majortrips1763> sent a code paste, see https://play.nim-lang.org/#pasty=xkNIdzJA
19:54:52FromDiscord<double_spiral> That goes beyond my expertise
19:58:35FromDiscord<majortrips1763> It is kinda surreal because my editor indicates that the format is right and it highlights the text and everything as expected, but the generated docs don't include the expected reference links.
20:04:18FromDiscord<majortrips1763> They don't work w/in the docs for an object field... ?
20:14:05FromDiscord<majortrips1763> Yah .. that is exactly the issue.. wild
20:18:32FromDiscord<aintea> Is there some other way than checking everyday the GitHub issue if ML-like pattern matching is added into Nim ?
20:18:49FromDiscord<Elegantbeef> Yea just forget about it
20:19:10FromDiscord<aintea> It's fun and all when macros do it but it's a pain in the flipping compiler when it errors
20:19:16FromDiscord<aintea> In reply to @Elegantbeef "Yea just forget about": Why ?
20:19:35FromDiscord<Elegantbeef> Cause it's not likely to suddenly exist
20:19:38FromDiscord<majortrips1763> sent a code paste, see https://play.nim-lang.org/#pasty=ppzDfqUO
20:19:52FromDiscord<aintea> The issue has been opened by araq in January of this year
20:20:50FromDiscord<aintea> Also do you believe ML-like pattern matching has some cons ? I only see pros but that means I'm wrong
20:20:51FromDiscord<Elegantbeef> That's' what I mean
20:26:17FromDiscord<Elegantbeef> It's just a statically typed variation over what is currently done
20:27:26*ntat quit (Quit: Leaving)
20:27:58FromDiscord<majortrips1763> So I guess parameter/field/member docs are just consumed "as is", no processing at all?
20:42:54*mahlon quit (Ping timeout: 252 seconds)
20:55:52FromDiscord<majortrips1763> Ahh .. found it: https://github.com/nim-lang/Nim/issues/12353
20:58:05FromDiscord<majortrips1763> Sooo .. yah .. docgen issues
21:15:54*mahlon joined #nim