Dual typeclass

Open

#3,367 opened on Mar 24, 2020 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language: Scala
Stars: 5.5k
Forks: 1.2k
Avg merge: 2d 10h
Merged PRs (30d): 5

Description

I am wondering whether it makes sense to add the Dual (aka Pairing) typeclass described here.
Its main use case is providing a pair between a DSL and its interpretation. You can see a very basic example here, and further work here.

Do you believe that it may belong to some cats module?

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Research direction

Read the linked Dual/Pairing typeclass description and the coscala and free-cofree examples first. Then review Cats' module organization to determine whether the proposal fits an existing module or needs a new design. Done means a concrete, agreed scope and module placement; the issue currently names no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack: scala
Domain: tooling
Issue type: Feature
Difficulty: 5/5
Estimated time: Over a week
Activity status: Stale
Clarity: Needs clarification
Newbie friendliness: 15/100

A short digest of beginner-friendly GitHub issues.