-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Consider changing collection constructors to accept iterables #11
Comments
I'm certainly open to this change. One of the ultimate goals of this package is to integrate with Base and be as familiar as possible. It's a way away from that, but sticking to the conventions present in Base is a big part of it. |
Cool. I would love to see these in Base at some point. |
@kmsquire could you check if this could be closed? Currently |
The constructors for |
Thanks for staying on top of this =) |
I think it's worth moving this package to the JuliaLang org, if you are willing, so that it gets more visibility (people might need it but not know it yet. ;) ) and other collaborators can collectively work on features. @StefanKarpinski what do you think? |
I'm definitely open to it if people would find it useful. I'm planning to do the same with FactCheck.jl. Most of my Julia projects are reasonably unmaintained at this point, which is a bummer. |
@zachallaun, you need admin rights here? |
@StefanKarpinski Got it. Moving this repo and FactCheck.jl to julialang. |
Coolio. Thanks for doing that. |
@StefanKarpinski All done, methinks. You can have your keys back now. |
Aight. Thanks again. |
Sweet. Just tagged v0.1.1 JuliaLang/METADATA.jl#1656 Thanks! :) |
A recent change in Base does this (JuliaLang/julia#5897), so that, e.g.,
Set(1,2,3)
is nowSet([1,2,3])
. This is mainly for efficiency--e.g., constructing from large collections no longer requires splatting:The text was updated successfully, but these errors were encountered: