`Vector` constructor is not exposed.

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
haskell
Domain
data

Research direction

Compare the public APIs of Data.Vector and Data.Vector.Primitive.Vector, focusing on constructor visibility and access to size and offset. Read the linked issue discussion first; the work is complete only when the project has a decided, documented API for these internals and the relevant behavior is covered.

Written by the indexing model from the issue text.

Description

I find it slightly confusing.

Data.Vector.Primitive.Vector constructor is exposed, but for Data.Vector it isn't. The inconsistency doesn't make sense to me, and I'd like to have internals (i.e. access to size and offset) exposed somewhere.

@lehins pointed somewher else (Reddit?) that quickcheck-instances doesn't generate sliced Vectors. But from current API of Vector it doesn't seem to matter, as far as I can see, there isn't a way to exploit slicedness of ordinary Vectors, (you can exploit slicedness of some other vectors, but not all).

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.