Newest at the top
| 2025-11-23 23:21:17 +0100 | takuan | (~takuan@d8D86B9E9.access.telenet.be) (Remote host closed the connection) |
| 2025-11-23 23:18:13 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-23 23:16:34 +0100 | peterbecich | (~Thunderbi@172.222.148.214) (Quit: peterbecich) |
| 2025-11-23 23:12:43 +0100 | j1n37 | (~j1n37@user/j1n37) j1n37 |
| 2025-11-23 23:09:42 +0100 | j1n37- | (~j1n37@user/j1n37) (Read error: Connection reset by peer) |
| 2025-11-23 23:07:13 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds) |
| 2025-11-23 23:06:20 +0100 | Sgeo | (~Sgeo@user/sgeo) Sgeo |
| 2025-11-23 23:05:32 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
| 2025-11-23 23:03:43 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Ping timeout: 240 seconds) |
| 2025-11-23 23:02:50 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-23 23:00:53 +0100 | jmcantrell | (~weechat@user/jmcantrell) jmcantrell |
| 2025-11-23 22:54:58 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2025-11-23 22:52:44 +0100 | ouilemur | (~jgmerritt@user/ouilemur) ouilemur |
| 2025-11-23 22:51:41 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-11-23 22:50:06 +0100 | Sgeo | (~Sgeo@user/sgeo) (Ping timeout: 256 seconds) |
| 2025-11-23 22:49:56 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection) |
| 2025-11-23 22:47:28 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-23 22:45:46 +0100 | Googulator85 | (~Googulato@2a01-036d-0106-01f1-f56c-45b8-e3c8-fdbd.pool6.digikabel.hu) (Quit: Client closed) |
| 2025-11-23 22:45:46 +0100 | Googulator50 | (~Googulato@2a01-036d-0106-01f1-f56c-45b8-e3c8-fdbd.pool6.digikabel.hu) |
| 2025-11-23 22:44:19 +0100 | trickard_ | (~trickard@cpe-87-98-47-163.wireline.com.au) |
| 2025-11-23 22:44:06 +0100 | trickard_ | (~trickard@cpe-87-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2025-11-23 22:42:01 +0100 | jmcantrell | (~weechat@user/jmcantrell) (Ping timeout: 264 seconds) |
| 2025-11-23 22:36:38 +0100 | jmcantrell | (~weechat@user/jmcantrell) jmcantrell |
| 2025-11-23 22:36:34 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds) |
| 2025-11-23 22:32:05 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-23 22:23:41 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-11-23 22:19:51 +0100 | ouilemur | (~jgmerritt@user/ouilemur) (Quit: WeeChat 4.7.0) |
| 2025-11-23 22:17:33 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2025-11-23 22:17:14 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-23 22:16:16 +0100 | Nachtgespenst | (~user@user/siracusa) siracusa |
| 2025-11-23 22:13:09 +0100 | <int-e> | While a FUN is basically just a pointer to a piece of code that can be jumped into once all the arguments are supplied and put on the stack |
| 2025-11-23 22:12:47 +0100 | <[exa]> | *phew* |
| 2025-11-23 22:12:40 +0100 | <[exa]> | ok |
| 2025-11-23 22:12:38 +0100 | <[exa]> | ah yes otherwise it's FUN. |
| 2025-11-23 22:11:28 +0100 | <int-e> | Well, not really because a PAP always has at least one argument applied. |
| 2025-11-23 22:11:12 +0100 | infinity0 | (~infinity0@pwned.gg) infinity0 |
| 2025-11-23 22:09:35 +0100 | infinity0 | (~infinity0@pwned.gg) (Remote host closed the connection) |
| 2025-11-23 22:08:16 +0100 | <[exa]> | if I got it right |
| 2025-11-23 22:08:11 +0100 | <[exa]> | oh these are for small functions, like PAP but nicely static without the extra metadata? |
| 2025-11-23 22:07:49 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 264 seconds) |
| 2025-11-23 22:06:37 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-11-23 22:03:52 +0100 | <int-e> | (FUN* objects are unapplied; the distinction is made to support function applications in the mutator, not for the benefit of GC) |
| 2025-11-23 22:03:43 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2025-11-23 22:03:35 +0100 | <[exa]> | I recall some paper that did like 16 variants of these for all combinations of packed&unpacked things |
| 2025-11-23 22:03:18 +0100 | humasect_ | (~humasect@dyn-192-249-132-90.nexicom.net) (Read error: Connection reset by peer) |
| 2025-11-23 22:03:07 +0100 | <int-e> | I should use CONSTR_ for this |
| 2025-11-23 22:03:01 +0100 | <int-e> | hmm |
| 2025-11-23 22:03:00 +0100 | <[exa]> | oh so it's a shortcut essentially. OK |
| 2025-11-23 22:02:42 +0100 | <int-e> | Stuff like FUN_0_1 exists for small arities to avoid this extra lookup. |
| 2025-11-23 22:02:10 +0100 | <int-e> | [exa]: Well stuff like "FUN" looks at more data in the info table to figure out which heap object fields are pointers and which are nonpointers. So it's not *just* the type. |