JuliaArrays / JuliaArrays/StaticArrays.jl

`@SArray` is sometimes not consistent with Base

Open
#1,215 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

julia> using StaticArrays

julia> @SArray [1:3;]
1-element SVector{1, UnitRange{Int64}} with indices SOneTo(1):
 1:3

julia> [1:3;]
3-element Vector{Int64}:
 1
 2
 3

julia> @SArray [(1:3)...]
1-element SVector{1, Tuple{Int64, Int64, Int64}} with indices SOneTo(1):
 (1, 2, 3)

julia> [(1:3)...]
3-element Vector{Int64}:
 1
 2
 3

I'm not sure we need to support these calls, and it would be better to throw errors than the current behaviors.

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 reproducing the two @SArray examples shown in the issue and compare them with the corresponding Base array expressions. Trace the @SArray entry point to determine whether these inputs should be supported or rejected; done means the behavior is intentionally consistent with Base or produces clear errors for the unsupported cases.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.