browserify/rustify

Map JS Types to Rust

Open

#5 opened on Nov 27, 2017

View on GitHub
 (5 comments) (2 reactions) (0 assignees)JavaScript (495 stars) (25 forks)batch import
enhancementhelp wanted

Description

Currently we only support passing i32 integers — great for math, but having more options would be great! We should probably look into rust-experiments and add some of the things they're doing.

Also s/o to @killercup for giving pointers to get in the right direction! 🙏

See Also

Contributor guide

Tech stack
javascriptrustwasm
Domain
build systemtooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of Rust and JavaScriptFamiliarity with WebAssembly
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Review the existing type mapping in the rustify transform code (likely in the main source file). Investigate the wasm experiments repository linked in the issue to understand how they map additional JavaScript types (e.g., strings, floats) to Rust. Identify which types are most requested or easiest to implement. Then implement support for at least one new type, following the patterns from wasm experiments.