IntersectMBO/plutus

Use type-level Nats for `safeEncodeBits`

Open

#6,048 opened on May 17, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Haskell (1,637 stars) (511 forks)batch import
Good first issueInternalPlutus Corestatus: triaged

Description

Right now safeEncodeBits act like a C-assertion. Use instead GHC.TypeLits/DataKinds to enforce safety statically.

Contributor guide

Tech stack
None
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
HaskellGHC type level programmingDataKindsPlutus core
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Examine the implementation of `safeEncodeBits` in the Plutus source code. Investigate how GHC.TypeLits and DataKinds can be used to lift bit length constraints to the type level, removing the need for runtime assertions. Look at existing uses of type level naturals in the codebase for guidance.
Use type-level Nats for `safeEncodeBits` · IntersectMBO/plutus#6048 | Good First Issue