Fix most strong mode warnings.

lib/src/result/error.dart

Index: lib/src/result/error.dart
diff --git a/lib/src/result/error.dart b/lib/src/result/error.dart
index eecf68e450c873cfee8aac7a019dde4bc6c7f871..b6d585937f520f736cd77d322945bb6796722649 100644
--- a/lib/src/result/error.dart
+++ b/lib/src/result/error.dart
@@ -8,14 +8,14 @@ import '../result.dart';
 import 'value.dart';
 
 /// A result representing a thrown error.
-class ErrorResult implements Result {
+class ErrorResult<T> implements Result<T> {

[Lasse Reichstein Nielsen, 2016/03/29 21:53:59]

I really dislike adding <T> here - it's completely unnecessary since the class
doesn't use it for anything.

An ErrorResult is a Result<T> for any <T>, which is why it was declared as
Result<dynamic>. That's actually accurate - if you get an error from a
Future<int>, you should be able to make a Future<String> with the same error
without the error enforcing the type of the future unnecessarily.

[nweiz, 2016/03/30 00:57:18]

I understand the logic behind this being a Result<dynamic>, but it just doesn't
work with strong mode. In strong mode, Result<dynamic> is! Result<T> for any T
other than dynamic.

   final error;
   final StackTrace stackTrace;
 
   bool get isValue => false;
   bool get isError => true;
-  ValueResult get asValue => null;
-  ErrorResult get asError => this;
+  ValueResult<T> get asValue => null;
+  ErrorResult<T> get asError => this;
 
   ErrorResult(this.error, this.stackTrace);
 
@@ -27,7 +27,7 @@ class ErrorResult implements Result {
     sink.addError(error, stackTrace);
   }
 
-  Future get asFuture => new Future.error(error, stackTrace);
+  Future<T> get asFuture => new Future.error(error, stackTrace);

[Lasse Reichstein Nielsen, 2016/03/29 21:53:59]

Should this be  new Future<T>.error ?
(Then, at least, the type is used for something).

[nweiz, 2016/03/30 00:57:18]

That's inferred via downward inference.

[Lasse Reichstein Nielsen, 2016/03/30 16:00:18]

That doesn't work in the VM or pure Dart.

This code should be Dart (non-strong-mode) compatible, and if the return type
says Future<T>, then it should return a Future<T>, which it doesn't as written.

[nweiz, 2016/03/30 19:11:54]

I'm not sure what you mean by "pure Dart", but this does work in the VM. In
checked mode, `Future<generic> is Future<T>`.

 
   /// Calls an error handler with the error and stacktrace.
   ///