From 0cdc09706a928e3c5a4543ec1f1a19f5f93a2208 Mon Sep 17 00:00:00 2001 From: Justin Ethier Date: Thu, 11 Feb 2016 22:35:09 -0500 Subject: [PATCH] Cleanup --- gc-notes.txt | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/gc-notes.txt b/gc-notes.txt index 3d628670..9c38e4e5 100644 --- a/gc-notes.txt +++ b/gc-notes.txt @@ -13,20 +13,12 @@ TODO: - read.sld in-port-table - obvious thread safety issue here what is the performance impact of adding locks to all these funcs? or do we need to rewrite the code somehow? - - start making core stuff thread safe. for example, test.scm sometimes - crashes, I think printing out result from (read) + - start making core stuff thread safe - assume I/O and eval both have threading issues - eval.sld - ... - In conjunction with above, write more programs that use multiple threads - - try a simple one with 3-6 threads just writing data to output, and then files - simple multithreaded example such as producer/consumer - find at least one more algorithm that can be parallelized -- document at a high level how the GC works - mostly what minor/major GC's are, and how they are interleaved. -- user manual - need to document everything, including: - - what to be cognizant of when writing threading code. esp, how to deal with stack objects (initiating minor GC's, etc) - this probably should be part of the user manual itself - revisit features list, issues list, etc DONE: