I've been enabling lints, http://dart-lang.github.io/linter/lints/, through .analysis_options and seeing how my codebase does. I ran the flutter specific ones and they seem to be in opposition to the standard practices that have been pushed by the Dart team. I actually got out of the habit of typing everything and moving to var but that seems to be something the flutter team does not want to do. Is there a particular benefit to this if I have a library that I would want to run in flutter?Basically with this and strong mode I'm really not sure how my code should look.
Sounds great!
--
For other discussions, see https://groups.google.com/a/dartlang.org/
For HOWTO questions, visit http://stackoverflow.com/tags/dart
To file a bug report or feature request, go to http://www.dartbug.com/new
---
You received this message because you are subscribed to the Google Groups "Dart Misc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to misc+uns...@dartlang.org.
I think the bigger surprise was that "as" was enough of an overhead that they were avoiding it. Is it that dramatic a slowdown? I ask because I tend to use it quite a bit especially when coding Polymer.dart.
That is good news Bob!I've been thinking about your arguments about not using types, and with strong mode not using types makes much more sense.Only thing I really miss though, is more support of the editor, it should quickly able to tell me what the type of a variable is.Just by hovering some variable for example.
factory FooElement() =>
new Element.tag('foo-element') as FooElement;
The Flutter team has asked us for a more general static cast (e.g., C++'s with no runtime cost) to quiet strong mode
– bob
Right. According to Srdjan, my comment about the compiler taking advantage of an "as" to optimize, does not apply to the Dart VM.Here's a tracking issue on static cast: