mcabbott / mcabbott/LazyStack.jl

`Base.stack`

Open
#13 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Julia
Stars
29
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Now that https://github.com/JuliaLang/julia/pull/43334 is merged, and available on Compat.jl, this package needs to decide what to do.

  • Perhaps the lazy struct is still useful for some purposes. If the next step is broadcasting, then this can be fast.
  • The eager code should just be deleted, and call Base. This was supposed to be called automatically on e.g. a stack of CuArrays, but I'm not sure that works right now.
  • The name stack should not be exported. Should it be LazyStack.stack, or export lazystack?

Edit: Mostly done in https://github.com/mcabbott/LazyStack.jl/pull/14 now. The remaining piece is:

  • Base supports dims which the lazy struct does not. Perhaps it should learn, in order to have exactly the same rules?

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 reading Julia's Base.stack behavior and the LazyStack lazy struct, including the changes described as mostly complete in pull request 14. Determine how the lazy struct should support the Base dims argument; done means its dimension rules match Base.stack.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.