Ziggit

SafeAllocator on wasm32-wasi (opens in new tab)

There is this in std/start.zig: const use_safe_allocator = !is_wasm and switch (builtin.mode) { .Debug, .ReleaseSafe => true, .ReleaseFast, .ReleaseSmall => !builtin.link_libc and builtin.single_threaded, // Also not ideal. }; What is the rationale behind the !is_wasm check? I can’t find any unsupported feature in the implementation, but maybe I’m missing something. Maybe it is because wasm programs usually aren’t long-lived, or to save memory, or something along those lines?

Read the original article
Sign in to keep reading the full article.

Keyboard Shortcuts

Navigation

Next / previous post
j/k
Open post
oorEnter
Preview post
v

Post Actions

Love post
a
Like post
l
Dislike post
d
Undo reaction
u
Save / unsave
s

Recommendations

Add interest / feed
Enter
Not interested
x

Go to

Home
gh
Interests
gi
Feeds
gf
Likes
gl
History
gy
Changelog
gc
Settings
gs
Discover
gb
Search
/

General

Show this help
?
Submit feedback
!
Close modal / unfocus
Esc

Press ? anytime to show this help