Version 1.0 ASAP (and hive like std::hive aka coolony) #946
Description
I see 0.19 was just out, and while it had breaking changes, and is meant to be last version before 1.0 (since 2022, that plan still valid?), can't we do 1.0 now/ASAP?
[People are likely adding 0.19 as compat as we speak, and might be good to add 1.0 at the same time, why wasn't the nest version chosen to be 1.0 not 0.19?]
I think you're aiming for perfection, but there's nothing wrong with doing a 1.0, even if more breaking happens, then just 2.0 (or avoid breaking as I suggest below).
I would think this package is a key package, even the key Julia package, and seeing pre-1.0 for it and commonly used datastructures, might be off-putting to users.
I think most of the datastructures are likely very stable already, only some less used less stable?
What I see e.g. breaking:
DisjointSets renamed to DisjointSet (singular form) (#700)
..
enqueue! → push!
Going forward, for the latter type of breakage, we can keep the old API as a synonym, only with redundant functions, thus no breakage, or need for a new major version number.
[C++26 has std:: hive, and it seems very intriguing, in case I can nerdsnipe anyone to make it... Since it's new it's not really about 1.0, unless it's done, and incorrectly the first time around...]