On Sat, Jun 27, 2015 at 7:29 AM, Nick Wellnhofer <[email protected]> wrote:
> it would be nice to make a 0.5.0 release this summer. For this release, I'd > like to finish the review of the public Clownfish API and add documentation > of the Clownfish header language and the runtime C API. +1 I'm content that we have a plan in place to address the inaccuracies of our inheritance/polymorphism model, and that's made me feel better about releasing. The other reform I think it's problematic to put off is firming up how we name and treat parcels. Parcel structure and polymorphism model impact how you organize and think about large projects. It would be a bummer if the current flawed approaches congeal. > We already reviewed the following classes: > > - Hash and HashIterator > - Obj > - Vector > > We still have to review: > > - Blob and ByteBuf > - Class and Method > - Err > - Num > - String and CharBuf > - Util/Memory > - Util/SortUtils > - Util/StringHelper > > Anything else we should address in 0.5.0? Not in 0.5.0. It would be nice to get Go bindings to a more mature state, and I hope to make that happen. However, if everything else is ready, the Go bindings should not block the release. > After 0.5.0, we could concentrate on interfaces and error handling. Works for me. I would also like to focus on adding more languages, but I'll go with the flow of volunteer energy. Marvin Humphrey
