From 6f51b414d31ea2722a5d65d15aad44c4c23e6da8 Mon Sep 17 00:00:00 2001 From: Tushar Mathur Date: Fri, 9 Aug 2024 09:36:44 +0530 Subject: [PATCH] update doc --- blog/tailcall-n+1-working-2024-08-04.md | 1 - 1 file changed, 1 deletion(-) diff --git a/blog/tailcall-n+1-working-2024-08-04.md b/blog/tailcall-n+1-working-2024-08-04.md index 34715491d4..4399c3af9c 100644 --- a/blog/tailcall-n+1-working-2024-08-04.md +++ b/blog/tailcall-n+1-working-2024-08-04.md @@ -188,7 +188,6 @@ The chunk data structure has the following properties: - `O(1)` complexity for append and concat operations. - Uses Reference Counting instead of Boxing to make cloning faster. - Can be converted to a vector of references to the elements in the chunk. -- Allocates ZERO heap of its own. You can clearly see that we don't actually perform an append or a concat operation instead we store a representation of that operation. This is a significant optimization because while performing the DFS, we create a lot of temporary query paths. However with the chunk data structure we don't need to allocate any additional memory on the heap or perform any form of wasted computation for paths that don't produce an N+1 query.