Post B0LeP8aFwDB14fgYjI by ar@is-a.cat
 (DIR) More posts by ar@is-a.cat
 (DIR) Post #B0LeP5MJvZFN4a8t5k by ar@is-a.cat
       2025-11-16T22:47:17Z
       
       0 likes, 0 repeats
       
       what if… rewrite-it-in-rust… again, from scratch?
       
 (DIR) Post #B0LeP6VZeeF8dZTn9c by ar@is-a.cat
       2025-11-16T22:49:33Z
       
       0 likes, 0 repeats
       
       that project would really benefit from a clean-er design
       
 (DIR) Post #B0LeP7Vxug9Nl4fcP2 by ar@is-a.cat
       2025-11-16T22:51:23Z
       
       0 likes, 0 repeats
       
       and splitting it up into parts properly.
       
 (DIR) Post #B0LeP8aFwDB14fgYjI by ar@is-a.cat
       2025-11-17T01:20:58Z
       
       0 likes, 0 repeats
       
       cargo workspaces are kinda silly
       
 (DIR) Post #B0LeP9SUgYYtmt3sGm by ar@is-a.cat
       2025-11-17T10:23:08Z
       
       0 likes, 0 repeats
       
       it's async. it's all async. you can't do shit with this without async. :blobcatangry:
       
 (DIR) Post #B0LePAVim2jn3BZxwG by ar@is-a.cat
       2025-11-17T15:50:59Z
       
       0 likes, 0 repeats
       
       «A no I/O state machine»looks insidedoes I/O with async funcs.
       
 (DIR) Post #B0LePBm44lPAyAEX3I by ar@is-a.cat
       2025-11-17T20:42:40Z
       
       0 likes, 0 repeats
       
       I guess i'm not going to escape the async :blobcatsad: and, on top of that, I'm probably going to have to use linkme::distributed_slice again. but at least this time i hope to have a decent excuse to do so.
       
 (DIR) Post #B0LePCw1lCy6ZLu0Dg by ar@is-a.cat
       2025-11-17T20:53:55Z
       
       0 likes, 0 repeats
       
       and, once again, i've had an OOM because of rust-analyzer.… I want to have 128G of ram in the next laptop I'm buying, whenever that happens.
       
 (DIR) Post #B0LePDroINBnSYw9Hk by APPTeOORuzvlGOetVY.verita84@poster.place
       2025-11-17T20:54:31.391032Z
       
       0 likes, 0 repeats
       
       @ar Sounds like it's not memory safe after all :seinfeld: