# Scope for Work on Racket -\> WASM?

**URL:** <https://racket.discourse.group/t/scope-for-work-on-racket-wasm/3556>\
**Category:** Questions & Answers\
**Created:** [February 10, 2025, 1:00pm UTC](https://racket.discourse.group/t/scope-for-work-on-racket-wasm/3556 "2025-02-10T13:00:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![GunpowderGuy](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/gunpowderguy/32/2192_2.png) [@GunpowderGuy](https://racket.discourse.group/u/GunpowderGuy)\
**Post date:** [February 12, 2025, 2:52am UTC](https://racket.discourse.group/t/scope-for-work-on-racket-wasm/3556/2 "2025-02-12T02:52:10Z")

</div>

There was a paper "rasm" about compiling racket to wasm. It posits that chez scheme, the language racket compiles to, could use some changes to better support a wasm backend.

Another option would be to directly target wasm instead of using chez scheme, as native code generation does.There is an alternative backend "Nora" that attempts to do this with llvm

Btw : i have a related thread [WASM Proposal Lacks Support for Reusable Continuations](https://racket.discourse.group/t/wasm-proposal-lacks-support-for-reusable-continuations/3553)

---

_[View the full topic](https://racket.discourse.group/t/scope-for-work-on-racket-wasm/3556)._