Bob Nystrom b504fd428c Fix covariant overrides in SynchronousFuture. (#5262)
* Fix covariant overrides in SynchronousFuture.

There were two things going on here. In timeout(), the callback's return
type was needlessly tightened to only allow callbacks that return
futures. This makes SynchronousFuture not substitutable with Future,
whose timeout() allows callbacks that return immediate values.

Since SynchronousFuture.timeout() never calls the callback anyway, I
just loosened it to match Future.timeout().

SynchronousFuture.whenComplete() is just wrong. The type error, again,
is that the callback's return type is too tight. Future.whenComplete()
allows synchronous callbacks.

But the actual implementation is wrong as well. whenComplete() should
return a future that completes to the *original value*, not whatever the
callback returns.

So I just fixed the method to work correctly, including handling
callbacks with synchronous results.

* "(error, stackTrace)" -> "(e, stack)".
2016-08-05 15:18:07 -07:00
2016-08-05 00:16:44 -07:00
2016-07-12 12:53:47 -07:00
2016-04-08 10:25:41 -07:00
2016-03-25 20:17:22 -07:00
2015-10-30 11:16:58 -07:00
2016-07-27 13:45:58 -07:00

Flutter

Join Gitter Chat Channel - Build Status - Coverage Status -

Flutter is a new way to build high-performance, cross-platform mobile apps. Flutter is optimized for today's, and tomorrow's, mobile devices. We are focused on low-latency input and high frame rates on Android and iOS.

Flutter is an early-stage open-source project. We are still missing core features like accessibility, text input, localization, and more. However, you can build demos and examples today. We hope you try it out and send us feedback.

Community

Join us in our Gitter chat room or join our mailing list, flutter-dev@googlegroups.com.

Description
A vendored version of the flutter engine for firka :3
Readme 323 MiB
Languages
Dart 75.4%
C++ 16.4%
Objective-C++ 2.7%
Java 2.7%
Objective-C 0.6%
Other 1.8%