Post B6cJQhf2cr8VHa4bVg by delta@mk.absturztau.be
 (DIR) More posts by delta@mk.absturztau.be
 (DIR) Post #B6cJQhf2cr8VHa4bVg by delta@mk.absturztau.be
       0 likes, 0 repeats
       
       @nelson@wetdry.world @mildsunrise@tech.lgbt i get both sentiments tbhpersonally i do think higher level things like time/date or hashmaps should be included in a standard library, I'd rather have a good baseline implementation of these things rather than every other project having it's own  slightly different implementation of varying qualityas long as there is no hard requirement to use it I'd rather have more in an stdlibbut i also don't think these things need to be in the core of a standard library, i think the core should be as lean as possible, with the other niceties being included in more self contained modular parts, where it's up to you if you want them or not
       
 (DIR) Post #B6cJQhr5u2mFsxiEIS by natty@astolfo.social
       0 likes, 0 repeats
       
       @delta@mk.absturztau.be @nelson@wetdry.world @mildsunrise@tech.lgbt why were we untagged from the thread? ​:neofox_woozy:​ Yeah I think the stdlib could totally be two-stage, the std and core. But I guess with explicit allocators this is less of a concern
       
 (DIR) Post #B6cJZN94GvEMGDFfMm by delta@mk.absturztau.be
       1 likes, 0 repeats
       
       @natty@astolfo.social @nelson@wetdry.world @mildsunrise@tech.lgbt no idea, i woulda rebooped but i only noticed after i hit send
       
 (DIR) Post #B6cLgJK557c6LCq5aq by natty@astolfo.social
       0 likes, 0 repeats
       
       @delta@mk.absturztau.be @nelson@wetdry.world @mildsunrise@tech.lgbt but yeah basically the idea is that having it be in the required core part would be annoying for embedded where you're very likely to justNever use this stuff at all