IntersectMBO/plutus

Data.AssocMap and Data.Value should use Data.List

Open

#6,933 opened on Mar 10, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Haskell (511 forks)batch import
Good first issueInternalPlinthPlutus Ledger APIstatus: triaged

Repository metrics

Stars
 (1,637 stars)
PR merge metrics
 (Avg merge 6d 1h) (15 merged PRs in 30d)

Description

After https://github.com/IntersectMBO/plutus/pull/6931 is merged, you can search for uses of toSOPList or unsafeFromSOPList and you'll see that lots of code in the ledger API or the standard library does conversions to and from SOP lists which is not ideal. This is because when we implemented Data-backed Map and Value, we didn't have a Data-backed List yet. We should refactor all of these cases where a Data-backed List would be more appropriate.

Contributor guide

Research direction
Search for uses of `toSOPList` and `unsafeFromSOPList` in the ledger API and standard library. After PR #6931 is merged, refactor each occurrence to use Data backed List types where appropriate. Check the Plutus repository's Data module for available list types. Ensure that the refactoring passes all existing tests.
Tech stack
None
Domain
data
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PR #6931 mergedKnowledge of Plutus Data typesFamiliarity with ASSOCMAP and VALUE modulesUnderstanding of SOP lists
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40