Reduce sd2k/brush fork divergence

Open
#33 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust, wasm
Domain
build-system, operating-systems

Research direction

Start with Cargo.toml lines 52-53 and read patches/brush-subprocess.patch, focusing on the thread_local spawn handler and WASI dispatch. Compare the sd2k/brush fork on branch more-wasi-compat with the upstream dependency. Done means the patches are upstreamed, or the fork divergence is documented and minimised so the project is no longer unnecessarily tied to it.

Written by the indexing model from the issue text.

Description

dependencies subprocess

Cargo.toml:52-53 use the sd2k/brush fork (branch more-wasi-compat) plus patches/brush-subprocess.patch (thread_local spawn handler + WASI dispatch). Upstream the patches or document/minimise the divergence so we're not stuck on a fork.

Dominant language
Rust
Stars
9
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 sd2k/conch

All issues in sd2k/conch

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.