WebAssembly / WebAssembly/spec

WebAssembly proposals mechanization and writeup

Open
#1,739 1 comment 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
WebAssembly
Stars
3.5k
Forks
539
Avg merge
2d 1h
Merged PRs (30d)
13

Description

Apologies if this is a bad place to post this, I had a tough time deciding which repo would be most fitting.

For my CS Master's thesis I built upon @conrad-watt's Isabelle WebAssembly mechanization and added three proposals: non-trapping float to int, sign extension operators, and tail call. Conrad has (very understandably!) been busy finishing his own (PhD!) thesis, so this hasn't been extensively vetted by anyone better at Isabelle than I. Once he is more available we can hopefully integrate these changes into the published AFP proof.

The source for the mechanization can be found here: https://github.com/jacobmischka/wasm-isabelle

My thesis/writeup on the project and WebAssembly and mechanization as a whole can be found here: https://github.com/jacobmischka/uwm-masters-thesis/releases/tag/1.0.0

Sorry if this comes off as self-advertisement, that's not my intention at all, I just wanted to share my work in case it's deemed useful or interesting.

Thank you! I'm extremely grateful to have been a small part of this community, and hope I might be able to become a larger part now that I've finished my degree and have some more free time.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked wasm-isabelle source and the thesis/writeup, then compare the three listed proposals—non-trapping float to int, sign extension operators, and tail call—with the published AFP WebAssembly proof. Done would require expert vetting and a clear path toward integrating the changes into the published AFP entry.

Written by the indexing model from the issue text.

Assessment

Tech stack
wasm
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.