| 00:15:22 | * | NimBot joined #nim |
| 00:23:49 | * | yeti joined #nim |
| 03:06:22 | * | rockcavera quit (Remote host closed the connection) |
| 03:37:33 | * | lucerne90 quit (Ping timeout: 268 seconds) |
| 05:11:19 | * | amadaluzia joined #nim |
| 09:26:09 | * | Skippy8 joined #nim |
| 09:47:10 | FromDiscord | <enthus1ast.> Does one know if `ForLoopStmt` is still needed? |
| 09:47:20 | FromDiscord | <enthus1ast.> for a macro that rewrites for loops? |
| 09:47:28 | FromDiscord | <enthus1ast.> i'm getting mixed signals 🙂 |
| 09:47:33 | * | amadaluzia quit (Read error: Connection reset by peer) |
| 09:48:39 | * | amadaluzia joined #nim |
| 09:57:44 | FromDiscord | <litlighilit> iirc, I just tried any compile flags i know.↵(@planetis_m) |
| 09:57:45 | FromDiscord | <litlighilit> but none works |
| 09:58:43 | FromDiscord | <litlighilit> gdb still always show me with the nim source |
| 12:42:10 | * | xet7 joined #nim |
| 13:39:01 | FromDiscord | <mratsim> In reply to @litlighilit "I need to gdb": --passC:-g |
| 13:39:44 | FromDiscord | <mratsim> In reply to @enthus1ast. "Does one know if": "still"? |
| 14:47:33 | FromDiscord | <enthus1ast.> In reply to @mratsim ""still"?": Yes different AIs are certain that this ForLoopStmt was replaced by just varargs[untyped], which sound reasonable, but I do not see any issues or or mention this tbh, so this might be a hallucination |
| 14:47:55 | FromDiscord | <enthus1ast.> (edit) "or" => "pr" |
| 14:55:37 | FromDiscord | <mratsim> In reply to @enthus1ast. "Yes different AIs are": they probably took one of my comment out of context |
| 14:57:21 | FromDiscord | <mratsim> In reply to @enthus1ast. "Yes different AIs are": when I wrote loop-fusion forLoopStmt didn't exist so I did everything with varargs untyped |
| 14:59:29 | FromDiscord | <enthus1ast.> sent a long message, see https://pasty.ee/OnbEYebc |
| 14:59:58 | FromDiscord | <enthus1ast.> But this is what I need |
| 15:03:26 | FromDiscord | <enthus1ast.> I see you use 'forZip' instead of the standard 'for' in loop fusion, I hoped I could make this without user facing workarounds tbh |
| 15:23:52 | FromDiscord | <alipolo17777> in what situations is no parentheses function invoke syntax recommended ? |
| 15:31:23 | Amun-Ra | imho it depends solely on your coding preference |
| 15:46:23 | FromDiscord | <Laylie> if you're talking about command syntax where the routine name is at the start of the expression, i pretty much only use it for very simple things like echo, styledWrite (?), collection.add, etc.↵when you add more sub-expressions it gets confusing at best and impossible at worst |
| 15:46:36 | FromDiscord | <Laylie> if you mean ufcs without parentheses, best to only use it for property-like things, procedures that dont do much computation, that you want to pretend are field access |
| 15:49:43 | FromDiscord | <Laylie> ^ these two categories are not mutually exclusive |
| 15:52:40 | Amun-Ra | and I try to use as little ( ) as possible |
| 15:56:56 | Amun-Ra | and prefer x.y over y x |
| 15:57:22 | Amun-Ra | (but the latter depends on what the constuction is) |
| 16:11:14 | * | Skippy8 quit (Ping timeout: 276 seconds) |
| 16:12:16 | * | Skippy8 joined #nim |
| 16:14:46 | FromDiscord | <Aceroph> does bigEndian## always return a big endian? like if i pass a big endian, will it remain the same |
| 16:31:12 | * | Skippy8 quit (Ping timeout: 246 seconds) |
| 16:31:42 | * | Skippy8 joined #nim |
| 16:32:28 | FromDiscord | <Laylie> endians.bigEndian## really means "little endian to big endian".↵if you look at the implementation you see it does nothing if the host is big endian, and swaps the endianness otherwise.↵vice versa for the littleEndian procs |
| 16:36:11 | FromDiscord | <Aceroph> excellent |
| 16:36:47 | FromDiscord | <Aceroph> but yeah it wouldve been smart to look at the imp |
| 16:37:11 | FromDiscord | <Laylie> endians.bigEndian## really means "host endian to big endian".↵if you look at the implementation you see it does nothing if the host is big endian, and swaps the endianness otherwise.↵vice versa for the littleEndian procs |
| 16:41:42 | Amun-Ra | bigEndian is just an enum value; it's always going to be bigEndian |
| 16:43:58 | FromDiscord | <Laylie> the endians.{little,big}Endian{16,32,64} procs |
| 16:44:27 | Amun-Ra | ah, I missed "##" |
| 16:45:57 | Amun-Ra | I use my own std/endians alternative (I needed one for js target) |
| 16:49:34 | * | Skippy8 quit (Ping timeout: 276 seconds) |
| 16:50:22 | * | Skippy8 joined #nim |
| 17:15:44 | * | amadaluzia quit (Read error: Connection reset by peer) |
| 17:16:24 | * | amadaluzia joined #nim |
| 18:16:15 | * | amadaluzia quit (Read error: Connection reset by peer) |
| 18:16:43 | * | amadaluzia joined #nim |
| 18:19:21 | * | amadaluzia quit (Read error: Connection reset by peer) |
| 18:22:41 | * | amadaluzia joined #nim |
| 18:42:58 | FromDiscord | <mratsim> In reply to @Aceroph "does bigEndian## always return": use endians2, the API is a bit more intuitive |
| 19:42:29 | * | blackbeard420 is now known as wpbirney |
| 20:20:18 | * | emery quit (Read error: Connection reset by peer) |
| 20:21:12 | * | emery joined #nim |
| 20:50:43 | * | Skippy8 quit (Ping timeout: 276 seconds) |
| 20:51:22 | * | Skippy8 joined #nim |
| 21:26:29 | * | Skippy8 quit (Ping timeout: 272 seconds) |
| 21:50:38 | * | jjido joined #nim |
| 22:03:09 | * | jjido quit (Quit: Client closed) |
| 22:57:29 | * | rockcavera joined #nim |
| 23:06:11 | * | amadaluzia quit (Read error: Connection reset by peer) |
| 23:15:03 | * | amadaluzia joined #nim |