Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 50 million developers.
Sign upHighlights
- Arctic Code Vault Contributor
Pinned
1,837 contributions in the last year
Activity overview
Contributed to
bytecodealliance/wasmtime,
rust-fuzz/arbitrary,
fitzgen/bumpalo
and 5 other
repositories
Contribution activity
July 2020
- fitzgen/wasmtime-py Python
- fitzgen/wasm-c-api C++
Created a pull request in bytecodealliance/wasmtime-py that received 5 comments
Rename `Val.__raw__` to `Val._raw`
Stylistically we shouldn't use double under for non-builtin fields.
+253
−253
•
5
comments
- C API tweaks for wasmtime-py
- CI: Rearrange CI jobs from longest-running to shortest
- Support reference types in the C API
- Support reference types in `Func::wrap`
- fuzzing: Enforce a maximum input length for `peepmatic_compile` target
- wasmtime: Support reference types in the Rust API
- fuzzing: Enable reference types by default
- wasmtime: Implement `table.fill`
- readme: Make "wasmtime-go" use monospace font
- wasmtime: Implement `global.{get,set}` for externref globals
- peepmatic: Be generic over the IR we are optimizing
- Enable reftypes tests on aarch64.
- Fix signature of wasmtime_module_new
- peepmatic: Add bnot operation
- Switch CI back to nightly channel
- Update wasmparser to 0.59.0
- Make wasmtime_environ::Module serializable
- peepmatic: add reminder by a power of two rule
- Add __dso_handle to exception list of deprecated export symbols
- Link to C API docs and make a landing page
- Expand top-level `wasmtime` crate docs
Created an issue in WebAssembly/reference-types that received 3 comments
`table.fill` needs to bounds check before executing `table.set`?
I want to
confirm my understanding of table.fill's intended semantics, and
double check my reading of table.fill's spec text.
It is my understand…
3
comments