__bytecode__ support?

Open
  • Is something wrong?
#88 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
compilers

Research direction

Start by reading the existing Rascal PCode syntax and the linked Flash __bytecode__ reference, then compare the unlabelled-jump example in the linked Ruffle pull request. The issue names no files or tests, so locate the compiler entry points for parsing and emitting PCode before estimating scope. Done means Rascal supports inline bytecode with the intended flexibility, including unlabelled jumps.

Written by the indexing model from the issue text.

Description

Flash's compiler supports the __bytecode__ function for inline bytecode, detailed here and in its linked posts. Compared to Rascal's PCode syntax, this can give more freedom such as unlabelled jumps, which are used in https://github.com/ruffle-rs/ruffle/pull/23160

Dominant language
Rust
Stars
22
Forks
2
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from Dinnerbone/Rascal

All issues in Dinnerbone/Rascal

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.