Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

/prog/ Challenge 2016

Name: Anonymous 2016-01-16 16:26

Implement a compile-time garbage collector for an existing* language, all (also existing*) implementations of which uses a runtime garbage collector.
The compiler must accept the same set of input programs as the existing* implementation(s) (of your choice).
The programs output by your compiler must behave identically to the original implementation (modulo memory management) and must be provably memory-leak free. (Demonstrably memory-leak free is acceptable if no submissions are provably so).

You will receive extra points for also implementing compile-time array bounds checking.

You have until 2016-12-31 23:59:59 UTC.

* As of 2016-01-16 00:00:00 UTC.

Name: Anonymous 2016-01-16 17:26

this is undecidable btw

Name: Anonymous 2016-01-16 18:08

>>2
Maybe you just need to be more decisive.

Name: Anonymous 2016-08-24 5:04

>>1
just let the program allocate as much memory as it wants, and free it all at the end.

no memory leak

Name: Anonymous 2016-08-24 5:22

I don't free(), I exit().

Name: Anonymous 2016-08-24 7:36

>>1
I "tried" doing this before but ultimately you can't get past the halting problem. The closest solution is the way Rust does it.

>>4
the OS already does that.

Name: Anonymous 2016-08-24 7:59

>>6
so you mean linus solved this problem in like 91

Don't change these.
Name: Email:
Entire Thread Thread List