| 01:53:35 | * | beholders_eye quit (Ping timeout: 240 seconds) |
| 02:25:39 | * | rockcavera joined #nim |
| 03:34:31 | * | xtr00 quit (Ping timeout: 264 seconds) |
| 07:01:39 | * | rockcavera is now known as Guest3167 |
| 07:01:39 | * | tiorock joined #nim |
| 07:01:39 | * | Guest3167 quit (Killed (uranium.libera.chat (Nickname regained by services))) |
| 07:01:39 | * | tiorock is now known as rockcavera |
| 08:08:19 | * | xtr00 joined #nim |
| 08:13:38 | * | SchweinDeBurg quit (Quit: WeeChat 4.8.0-dev) |
| 08:14:42 | * | SchweinDeBurg joined #nim |
| 08:16:44 | * | przmk quit (Remote host closed the connection) |
| 08:29:24 | FromDiscord | <vindaar> In reply to @bubblie "Is there anything in": I'd say whatever interests you can use some help, because we're arguably understaffed everywhere 🙃 |
| 09:35:30 | FromDiscord | <aethrvmn> I wonder how quickly the shift to compiler plugins vs macros will happen |
| 09:46:57 | * | hygo quit (Quit: WeeChat 4.6.3) |
| 10:08:38 | * | przmk joined #nim |
| 10:45:40 | * | przmk_ joined #nim |
| 10:46:20 | * | przmk quit (Ping timeout: 244 seconds) |
| 10:46:20 | * | przmk_ is now known as przmk |
| 11:07:15 | FromDiscord | <vindaar> I expect we'll get back old style macros in the not so distant future. Maybe slightly different features, but I'd be shocked if there wasn't anything close to a direct replacement or at the very least a higher level interface than the current plugin interface |
| 11:39:33 | * | beholders_eye joined #nim |
| 11:51:34 | FromDiscord | <aethrvmn> They will keep macros as a keyword for backwards compat tbh, but I still don't really understand how plugins will work, but if I do I dont think I will understand why macros will need to coexist↵(@vindaar) |
| 12:30:37 | FromDiscord | <zumi.dxy> i understand plugins as implemented today as a sort of nif preprocessor |
| 12:31:25 | FromDiscord | <zumi.dxy> read nif -> plugin does stuff with it -> output nif -> nimony replaces {.plugin.} call with output nif |
| 12:31:42 | FromDiscord | <zumi.dxy> (edit) "read nif ... ->" added "{.plugin.} call" |
| 13:20:25 | * | beholders_eye quit (Ping timeout: 264 seconds) |
| 13:21:47 | * | beholders_eye joined #nim |
| 13:41:56 | FromDiscord | <ieltan> Maybe `macro` could be implemented as a built-in that uses `{.plugin.}` under the hood? Sort of like how `func` is just `proc {.noSideEffect.}` but `macro` would instead be a simple API for using plug-ins. I dunno if that makes sense or if it's doable though |
| 13:57:55 | * | beholders_eye quit (Ping timeout: 240 seconds) |
| 14:04:27 | * | beholders_eye joined #nim |
| 14:17:30 | FromDiscord | <pmunch> I think that should be possible. It would definitely suck to lose macros in Nim v3.. |
| 14:18:14 | * | xet7 joined #nim |
| 14:44:46 | FromDiscord | <saint._._.> In reply to @pmunch "I think that should": Why would macros be lost? Is it being reconsidered ? |
| 14:50:31 | * | beholders_eye quit (Ping timeout: 240 seconds) |
| 14:52:44 | * | beholders_eye joined #nim |
| 14:56:54 | FromDiscord | <pmunch> Well Nim 3 focuses on "compiler plugins", not sure where macros fit into that picture |
| 14:58:46 | FromDiscord | <aintea> Can't objects inherit a `concept` in Nim3 ? |
| 14:59:20 | FromDiscord | <aintea> I read the whole documentation except the standard library and didn't find anything about "implementing" concept into an object like in Rust for example |
| 15:03:22 | FromDiscord | <aintea> Also, is there a reason Nim3 uses ARC and not ORC or something else ? I have no idea of the tradeoffs of each one so I would like to understand |
| 15:43:24 | * | om3ga quit (Ping timeout: 260 seconds) |
| 15:44:15 | * | om3ga joined #nim |
| 15:56:41 | FromDiscord | <rakgew> indeed I would love to keep the awesome macros in nim3, too.↵(@pmunch) |
| 16:00:27 | FromDiscord | <ma.troc> sent a long message, see https://pasty.ee/DgxOnudc |
| 16:17:28 | FromDiscord | <nasuray> In reply to @pmunch "Well Nim 3 focuses": I thought the updated plan was to implement macros prior to v3 release. It's at least included as "macros" here https://github.com/nim-lang/nimony/issues/1478 which I would assume is something shaped at least mostly the same as the current implementation |
| 16:24:23 | FromDiscord | <pmunch> In reply to @nasuray "I thought the updated": Ah, I might've been working with outdated information then. Good to know! |
| 16:44:00 | FromDiscord | <Buckwheat> oh hey pmunch! thanks for putting up with my BS with my Futhark patches eheh |
| 16:44:26 | FromDiscord | <Buckwheat> first thing I've contributed to tbh so I was a lil nervous... |
| 17:27:49 | * | hygo joined #nim |
| 17:52:14 | FromDiscord | <litlighilit> I debug via manually `source _nim-src_/tools/debug/nim-gdb.py` when gdb (as I use choosenim)...↵@ma.troc\: maybe ref↵https://litlighilit.notion.site/debug-nim↵(@ma.troc) |
| 18:04:52 | * | thunder quit (Remote host closed the connection) |
| 18:05:28 | * | thunder joined #nim |
| 19:01:16 | FromDiscord | <pmunch> In reply to @Buckwheat "oh hey pmunch! thanks": Bullshit? I didn't spot any bullshit 🙂 |
| 19:01:58 | FromDiscord | <Buckwheat> heh... I just wanted to help because I was trying to set it up on the 2 platforms and I thought I was capable↵(@pmunch) |
| 19:03:41 | FromDiscord | <ma.troc> In reply to @litlighilit "I debug via manually": Thank you very much! I just tried those options you have in that document. Especially the --cppDefine:N_LIB_PRIVATE seems to make everything work mostly as intended. Where did you get that information? I find it especially interesting that this is the difference between gdb refusing to load the binary at all and loading and processing it completely fine |
| 19:19:05 | FromDiscord | <ma.troc> hm, on mac it still doesn't work 100% it seems. gdb still doesn't like the binary and in lldb The line numbers go beyond the end of the real nim code, but I can live with developing/debugging inside a docker container for now |
| 19:52:33 | FromDiscord | <mjsdev> My dynamic scripting inside nim is nearly complete: https://github.com/mattsah/mininim/blob/main/tests/testScript.nim |
| 19:53:06 | FromDiscord | <mjsdev> Soon all the angels will cry |
| 20:05:53 | * | derpydoo joined #nim |
| 20:50:43 | * | xet7 quit (Remote host closed the connection) |
| 21:25:17 | * | derpydoo quit (Quit: derpydoo) |
| 23:43:57 | FromDiscord | <bubblie> In reply to @pmunch "Well Nim 3 focuses": Isnt part of what makes nim special its macro system as well? |
| 23:44:09 | FromDiscord | <bubblie> Idk why that’d be lost |
| 23:45:33 | FromDiscord | <bubblie> are nimony plugins structured to be better? |
| 23:46:56 | FromDiscord | <bubblie> Forgive me for not fully understanding |
| 23:48:48 | FromDiscord | <bubblie> Oh im rereading plugins |
| 23:49:10 | FromDiscord | <bubblie> It IS supposed to be better macros |
| 23:50:08 | FromDiscord | <litlighilit> I'd be crying if nim losts macro↵↵as at least I have to rewrite all of pysugar of nimpylib, which is painful |
| 23:51:12 | FromDiscord | <bubblie> Backwards compatibility should definitely exist, most languages do that |
| 23:51:36 | FromDiscord | <bubblie> It’d be weird if it was completely removed because it doesnt give devs enough time to port over either |
| 23:52:50 | FromDiscord | <bubblie> In reply to @litlighilit "I'd be crying if": You made nimpylib??? |
| 23:53:05 | FromDiscord | <bubblie> I was looking at that today! |
| 23:56:41 | FromDiscord | <litlighilit> tbh the original author is @yardanico-57cc39ea40f3a6eec06363a8\:gitter.im, though as of now maybe 80% of current code was my written (not really count) |
| 23:58:02 | FromDiscord | <Buckwheat> kinda noticed that in general Nim's community seems a lil tight-knit and that people who've made some fantastic libs all hang out here↵(@bubblie) |
| 23:59:05 | FromDiscord | <litlighilit> These days I'm working on NPython↵so fewer commits on pylib (for several months it's 1 release per month).Yet, yesterday I've just implemented list/set/dict comprenhension (yet not pushed) |
| 23:59:30 | FromDiscord | <Robyn [She/Her]> In reply to @litlighilit "These days I'm working": NPython? Are you implementing Python in Nim? |
| 23:59:58 | FromDiscord | <litlighilit> These days I'm working on [NPython](https://github.com/nimpylib/npython)↵so fewer commits on pylib (for several months it's 1 release per month).Yet, yesterday I've just implemented list/set/dict comprenhension (yet not pushed) |