Backpermute needn't have the same index container

Open
#563 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
haskell
Domain
data

Research direction

Start by locating the backpermute API and its current type constraint, then inspect its existing usages and tests. Check how boxed, storable, and unboxed vectors are represented at the call site. Done means backpermute accepts an index container type distinct from the source while preserving existing behavior and coverage for the reported cases.

Written by the indexing model from the issue text.

Description

I often times compute the indices I want to backpermute has an unboxed vector. But the call site requires that I use the same vector container as my source to do so. So I end up having to roll my own in the case that I have a boxed or storable vector. Would it be possible to make backpermute polymorphic in its index container type?

Dominant language
Haskell
Stars
401
Forks
145
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 haskell/vector

All issues in haskell/vector

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.