On 15/07/2013 3:59 PM, Jonathan S. Shapiro wrote: > > 1. I don't know the state of GC support, though I know it's improved. > Your pointer to CHICKEN is helpful. In the long term this is a > solvable problem. >
Seems they've made some good progress: http://llvm.org/docs/GarbageCollection.html#overview-of-available-features > But straightforward things often take months to debug and implement in > practice. For a long-term language building exercise, that may be > fine. For a quick bring-up it isn't, and even for a long-term effort, > there are major advantages for validating the language and starting to > build libraries by having a quick bring-up path. Hmm, I suppose I just consider "months" to be a quick bring-up timeframe for a stable BitC compiler! The CLR will probably get you 80% of the way there, but representing that last 20% of programs is a real pain. In particular, data structures that need to exploit layout for, eg. cache awareness or cache-obliviousness, can't be representing straightforwardly in the safe subset. You'll always have to add indirections unless you want to lose the benefits of the runtime infrastructure, like GC. If you're going CLR, let me know if you have any questions or need some pointers to libraries or something. I've been working with the CLR for many years now. My open source Sasa class library [1] also provides a number of functional idioms and other useful extensions if you want to start from a more functional foundation. Good luck! Sandro [1] http://higherlogics.blogspot.ca/2013/06/sasa-094-released.html _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
