> Awesome. Should we expect a tagged release with the committed-to-master fix > for #66 (and if I understand correctly, corresponding 10% performance > improvement in some cases?) any time soon?
Hei, If you want that, I could produce this release. Since it includes two rather radical API changes, I'd have to plunge into revising the documentation - which would keep me from other things. Show of hands, how much priority does a quick 1.4 release have for you guys? greetings, kaspar
