From 2e6fcdcb7c6bc787e531321b11b3c047b5d6699e Mon Sep 17 00:00:00 2001 From: Abhiroop Sarkar Date: Tue, 8 Jun 2021 23:07:34 +0200 Subject: [PATCH] Update Future_work.md --- doc/notes/Future_work.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/notes/Future_work.md b/doc/notes/Future_work.md index 8e24bc3d..225b9fd1 100644 --- a/doc/notes/Future_work.md +++ b/doc/notes/Future_work.md @@ -13,10 +13,14 @@ 1. Multiple containers. 2. Priorities on containers and tasks. 3. Time. Preferably some way of handling time that fits into the Channel abstraction. + i. One interesting idea - Have a hidden time process and the process gets blocked on that process which sends a message after time t. + ii. Timed channels - useful for implementing timeouts. Can we implement this simply using what we already have? +4. Study/experiment with efficient list representation in the heap (https://ieeexplore.ieee.org/document/1663507) ## Researchy 1. Memory management - Look into alternatives to a stop the world GC -2. \ No newline at end of file +2. Implement FRP as a library in CamIoT. Why? A: Utilising the send, recv primitives might help implementing push-based FRP. +3. How does the channel-based model extend to containers and distribution?