Skip to content

Towards v3.0 #101

Closed
Closed
@dkarrasch

Description

@dkarrasch

We have currently two PRs in the pipeline that are breaking and therefore require a major release. So I thought we should collect ideas on what to put in there to not have major release every month or so. Clearly, we will have

Furthermore, I'd suggest to include

  • Introduce specific show methods, add Base.parent overload #87 with the new show methods (I guess the only way to really get a feeling for whether it's good or not is to start using it and collect "annoyed" feedback, otherwise I feel this is too distant to form an opinion just by reviewing the PR)
  • a nice Documenter documentation, which then could nicely address Relation to other libraries #98 (That shouldn't be too hard: I'm planning to mainly cut our long README into more digestible pieces as a first approach.)

Anything else? Of course, if some hot PR comes in, there's nothing that stops us from merging it and releasing another v2.x. I'd hope to finish this some time in late August/early September. Any contributions/PRs/suggestions are more than welcome.

Have a good (rest of the) summer everyone!

EDIT:

  • I think we should relax the type of the output variable in the mul!s to AbstractVecOrMat. The following works perfectly fine with matrices in LinearAlgebra:
using LinearAlgebra
mul!(rand(5,1), rand(5,5), rand(5))

TODO:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions