From f541a2c550097e6649b14348b26c17499d45e679 Mon Sep 17 00:00:00 2001 From: Alon Zakai Date: Thu, 2 Nov 2023 12:54:24 -0700 Subject: [PATCH] Fix placeholder tweet number (#715) * Remove placeholder tweet number, and add tweet --- src/blog/wasm-gc-porting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/blog/wasm-gc-porting.md b/src/blog/wasm-gc-porting.md index 223c4a303..532687d9e 100644 --- a/src/blog/wasm-gc-porting.md +++ b/src/blog/wasm-gc-porting.md @@ -6,7 +6,7 @@ avatars: date: 2023-11-01 tags: - WebAssembly -tweet: '123456' +tweet: '1720161507324076395' --- A recent article on [WebAssembly Garbage Collection (WasmGC)](https://developer.chrome.com/blog/wasmgc) explains at a high level how the [Garbage Collection (GC) proposal](https://github.com/WebAssembly/gc) aims to better support GC languages in Wasm, which is very important given their popularity. In this article, we will get into the technical details of how GC languages such as Java, Kotlin, Dart, Python, and C# can be ported to Wasm. There are in fact two main approaches: