User avatar
φ @fiore@shrimptest.bedwetting.club
Admin
she/her cybervampire
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
IM GONNA NEED VERBAL CONFIRMATION THAT YOURE GRASPING THE DETAILS OF THIS AGREEMENT
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
re: boost pls, rust question @lz whats that
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
re: boost pls, rust question @lz it can still be turned into an array w try_into()
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
re: boost pls, rust question @snacks its not a range, its an array literal

[x; N] desugars to an array of N xs
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
re: boost pls, rust question @lz @sodiboo sucks that its nigjtly ugh
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
re: boost pls, rust question @sodiboo @lz oh i see
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
re: boost pls, rust question @sodiboo @lz wouldnt thr stack allocation still happrn ? i dont see why this would solve my issue
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
re: boost pls, rust question @paula8 bwaaa
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
re: boost pls, rust question @snacks but thats not an abstraction thats literally whats written in the code

its optimized away when the compiler is run in --release mode but still
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
re: boost pls, rust question @paula8 yeag not that
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
re: boost pls, rust question @lz what options would i have ? couldnt find anything , idont mind doing .try_into().unwrap() since checking for sizr is trivial anyways
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
re: boost pls, rust question @snacks yes it is ? a box is always heap allocated , so that macro would only skip the stack allocation
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
boost pls, rust question ok so today i found out something VERY annoying

doing
let big_array = Box::new([0; 1000000]);




stack overflows even tho a Box is heap allocated , because the compiler puts it all on the stack and
then moves it

does anyone know if theres a nicer way to do this ??? like smth that does the same magic that
vec! does , because only being able to do smth like this thru a Vec or thru manual unsafe calls feels very weird
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
@snacks gonna turn off n on the whole netcup datacenter
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
@yassie_j oh my god ?????
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
why tf is thr instance so slow today
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
@lz @kimapr oh yea lol i just tried . oh well
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
@yassie_j wdym the menu items are ai ???
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
@lz @kimapr yea u cant do that for a whole instance it seems
User avatar
φ @fiore@shrimptest.bedwetting.club
5mo
@lz @kimapr netshrimp moment