Closed rich-j closed 6 years ago
Hi and thanks for reporting!
They are really tightening the noose on me now :-)
I've pushed a change on ddc_compat
where all the previously overridden mapX/liftX operations are moved from the Applicative instance for a type to static methods on the type itself. For example, OptionMP.map2(some(1), some(2), (int a, int b) => a+b)
is now Option.map2(some(1), some(2), (int a, int b) => a+b)
.
I've also started to add some type specialized traverse/sequence operations, such as IList#traverseOption
here and there, which will eventually completely replace the generic traverse/sequence mechanism. These should work in a fully type safe way on both Dart 1 and 2.
Hope that keeps you going until the next Dart 2 dev release :-)
Thanks - our unit tests are running again in the VM. Also I was able to change some ugly code over to using traverseX
operations. Too bad they need to be specialized - I guess it's progress...
Google is in clean up mode since Dart 2 stable is "happening very soon". You may have already seen this: Getting ready for Dart 2, and making your packages look great on the Pub site!.
Upgrading to
Dart VM version: 2.0.0-dev.69.0 (Tue Jul 17 14:57:16 2018 +0200) on "macos_x64"
now causes failures when running unit tests under the VM. This seems similar to https://github.com/spebbe/dartz/issues/7. Using yourddc_compat
branch and still run fine under DDC. Here are the load errors that now cause all unit tests to fail when run in the VM: