Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Plutarch runtime: Upstream what can be upstreamed

Open
#133 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
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
haskell
Domain
blockchain

Research direction

Start by inspecting the lbr-plutarch implementation and its PMaybe, PEither, and PList definitions, then compare them with Plutarch's existing Scott and PlutusData forms. The issue is complete when the upstreamable pieces are identified and the redundant reimplementations are addressed; no file or test is named, so scope needs clarification first.

Written by the indexing model from the issue text.

Description

plutarch runtime

The lbr-plutarch reimplements PMaybe, PEither, PList which will confuse users that already have to deal with Plutarch's equivalent types in Scott and PlutusData form.

Dominant language
Haskell
Stars
32
Forks
1
PR merge metrics
No merged PRs in 30d

Getting set up

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 mlabs-haskell/lambda-buffers

All issues in mlabs-haskell/lambda-buffers

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.