JuliaArrays / JuliaArrays/StaticArrays.jl

map on SOneTo produces MVector rather than SVector

Open
#1,333 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Julia
Stars
844
Forks
159
Avg merge
3d 21h
Merged PRs (30d)
3

Description

It seems like this should produce an SVector:

julia> map(i -> i+1, SOneTo(3))
3-element MVector{3, Int64} with indices SOneTo(3):
 2
 3
 4

(similar to how map on an SVector returns an SVector).

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.

Research direction

Start by tracing the map dispatch for SOneTo and compare it with the map behavior for SVector. Confirm the expected result for the provided example, then add or update coverage so mapping over SOneTo returns an SVector rather than an MVector.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.