i.e. instead of:

Something like:

Future<T> invokeMethod<T>(String method, [dynamic arguments]) async {
  ...
  return result as T;
}

There are a lot of runtime errors being reported by errors:
dart-lang/pub-dev#1263 (comment)

The advantage here is that T can be filled in automatically in most cases:

// Automatically infers invokeMethod<bool>!
Future<bool> isEnabled() => invokeMethod('isEnabled');

... and I imagine this would be a non-breaking change, as a plus! This won't work for more complex types, like List<String>, but maybe that's either OK or some variants of invokeMethod could be added to help, for example:

• Future<List<T>> invokeMethodList<T>(...)
• Future<Map<K, V>> invokeMethodMap<K, V>(...)