Post B5TduYnyJsdrMcbsvY by fiore@brain.worm.pink
(DIR) More posts by fiore@brain.worm.pink
(DIR) Post #B5TcBZ3WRNH39krd8S by fiore@brain.worm.pink
0 likes, 0 repeats
HHHHUUUUHHHHHHHH???????https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3869.pdf
(DIR) Post #B5Tdnuv9h9aJvannvM by autumn@waltuh.cyou
1 likes, 0 repeats
@fiore woah woah woah this is awesome stuff !
(DIR) Post #B5TduYnyJsdrMcbsvY by fiore@brain.worm.pink
0 likes, 1 repeats
C2Y SWEEPRE: https://brain.worm.pink/objects/7f6d9f41-1a63-447a-943a-ba9ee4377df3
(DIR) Post #B5TkbVaik9ZjZdH4Zk by navi@social.vlhl.dev
1 likes, 0 repeats
@fiore i hate the name but otherwise neat(tho the author is not quite right about realloc, implementations do realloc in place if there's extra data there -- regardless, this would simplify not needing to track allocated size)
(DIR) Post #B5TkgrjNr7m1gdsgAi by fiore@brain.worm.pink
0 likes, 0 repeats
@navi eh , idont have anything against long routine names , but thrn again , im a rust person.imean thats true about realloc but thats impl dependent isnt it ? having something like this makes me rest easier ^^
(DIR) Post #B5Tkl80BIq4fJBlp0S by mia@shrimptest.0x0.st
0 likes, 0 repeats
@navi @fiore yeah, that’s also standard-defined behavior so idk if they actually read that part or if that part of the page ended up getting rolled into a joint
(DIR) Post #B5Tkl8DIW4Z9xruIS0 by fiore@brain.worm.pink
0 likes, 0 repeats
@mia @navi 4/20 today !
(DIR) Post #B5TlR52ahcTEHrtyN6 by mia@shrimptest.0x0.st
1 likes, 0 repeats
@fiore @navi i mean “don’t make the user duplicate the allocator’s work unnecessarily” is a sound proposal imo. that extra burden of responsibility tends to cause bugs
(DIR) Post #B5TlS4glUrqpU8APxY by fiore@brain.worm.pink
0 likes, 0 repeats
@mia @navi yea true