<< 22-11-2026 >>

00:13:17*acidsys quit (Ping timeout: 240 seconds)
00:15:05*acidsys joined #nim
00:18:36*fallback quit (Server closed connection)
00:32:29*fallback joined #nim
01:15:04*xtr00 quit (Ping timeout: 262 seconds)
02:29:01FromDiscord<zkopt_> sent a long message, see https://paste.rs/zIg4D
02:30:31FromDiscord<zkopt_> In reply to @aintea "If so then why": I know that --opt options in nim 2 is not totally same with passes C flags ↵↵what I know is that nim compiler do optimisation little and this may have effect on ↵and also there's opt flag in linker too
03:17:02*fallback quit (Quit: IRCNow and Forever!)
03:19:55*fallback joined #nim
03:25:22FromDiscord<ghazalialshafi> sent a code paste, see https://paste.rs/hG6T3
04:28:37*iwuvmika quit (Ping timeout: 246 seconds)
04:45:00*iwuvmika joined #nim
05:21:12*iwuvmika quit (Ping timeout: 260 seconds)
05:23:52*iwuvmika joined #nim
05:41:36*GnuYawk129703 quit (Server closed connection)
05:41:59*GnuYawk129703 joined #nim
07:02:36*tuxpaint quit (Server closed connection)
07:02:53*tuxpaint joined #nim
07:11:36*yeti quit (Server closed connection)
07:12:08*yeti joined #nim
07:59:36*_________ quit (Server closed connection)
07:59:57*_________ joined #nim
09:37:27*HaikuUser joined #nim
10:21:44*iwuvmika quit (Ping timeout: 264 seconds)
10:47:01*iwuvmika joined #nim
12:08:09*insanescholar_ quit (Remote host closed the connection)
12:22:58FromDiscord<griffith1deadly> In reply to @ghazalialshafi "I was working on": use profiler to get concrete places first
13:08:00*xtr00 joined #nim
13:10:17FromDiscord<TӨMΛ ☠> I assume difference between `Table[int, X]` and `OrderedTable[int, X]` is that the latter will order things based on the order keys were added↵But then, is there expected order `Table` uses? Like e.g. if keys are `int` type, will it then order them in a `1, 2, 3, 4` way, or will they just be randomly thrown around? Asking precisely for iteration over tables bc it kinda is important for my project
13:22:03FromDiscord<Laylie> sent a code paste, see https://paste.rs/Oi4Ue
13:57:00FromDiscord<ghazalialshafi> In reply to @griffith1deadly "use profiler to get": I did a lot of that, and valgrind and other too I am thinking that the remaining gap there (frames, oldyoung, trees) is Nim's allocator and reference-counting cost frames still runs about 3.95 G instructions against hxcpp's 2.34 G ram. I also dropped --experimental:vtables and mimalloc (no gain by instruction count). I am hitting limits but I have to solve it.
14:01:45FromDiscord<griffith1deadly> In reply to @ghazalialshafi "I did a lot": nim devel offers best allocator (better than mimalloc already) so depends on your algorythms, you either need preallocated arenas (or simply preallocate strings if size known without resize-after) /& string interning /& cursor & span approach like nif
15:45:32*iwuvmika quit (Ping timeout: 258 seconds)
15:54:21*xtr00 quit (Read error: Connection reset by peer)
15:55:41*xtr00 joined #nim
17:06:36*casaca quit (Server closed connection)
17:06:46*casaca joined #nim
17:17:36*tmpod quit (Server closed connection)
17:17:47*tmpod joined #nim
17:35:46*oculux quit (Ping timeout: 252 seconds)
17:48:26*ftajhii quit (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
17:50:36*tk quit (Server closed connection)
17:50:45*tk joined #nim
17:52:04*insanescholar_ joined #nim
17:56:05*ftajhii joined #nim
17:58:13*SchweinDeBurg quit (Quit: WeeChat 4.8.0-dev)
18:00:36*shanoaice quit (Server closed connection)
18:00:52*shanoaice joined #nim
18:30:07*VITALIK joined #nim
18:34:49*VITALIK quit (Ping timeout: 267 seconds)
18:45:29*SchweinDeBurg joined #nim