IntersectMBO / IntersectMBO/formal-ledger-specifications
Organise preludes (e.g. `PreludeMeta` vs `MetaPrelude`)
Open
- Dominant language
- Agda
- Stars
- 52
- Forks
- 20
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 7
Description
We now have `PreludeMeta` and `MetaPrelude`. There's probably some improvement to this structure that could be done at some point.
_Originally posted by @WhatisRT in https://github.com/input-output-hk/formal-ledger-specifications/pull/301#discussion_r1391358656_
Contributor guide
Research direction
Start by comparing the roles and uses of `PreludeMeta` and `MetaPrelude`, then read the originating discussion in pull request #301. Done means the project has an agreed, clearer prelude organization and the issue records that the duplication or naming confusion has been resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100