> There are different ways to handle this problem (monomorphization being an > especially attractive one, I think), but it seems to me that the simplest > solution for a 0.1 release to just have GC bail out when it discovers a > dynamically-sized frame on the stack. Is this okay with others?
Where bailing out means it simply allocates more memory and doesn't collect anything? I can imaging a long-running computation inside some generic function 'leaking' until it runs out of memory. Does every generic have a dynamically sized frame or only those who create locals of parameterized variables? I agree that for 0.1 we can probably live with this but it does seem like something that we can expect to trip up a few users. _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
