Günter Zöchbauer
Günter Zöchbauer
My point is that it shouldn't matter if `async` is used. When an asyc call is made and the returned Future is ignored, the linter rule should warn.
A 2nd rule would be good enough for me. I know that this rule is controversial because there valid cases where the returned future is ignored. Devs who don't want...
I still don't see a difference between not awaited Futures in functions marked or not marked with `async`. There is also no way to escape in functions marked `async` if...
> I don't just mean this as "You can't use the 'await' keyword" - I mean this as "You cannot accomplish the semantics of 'await' without returning the Future or...
Not sure about that. I think the issue is that a call to an async function looks the same as the call to a sync function, and in both cases...
> How do we escape? As far as I remember assigning the Future to a variable is a way to opt out ```dart var _ = iosink.close(); ``` or an...
@foobnix Thanks, that fixed it. Feel free to close if there is nothing to fix.
I stumbled upon this with refinery, barrel, diesel. The features change often with new versions and are therefore cumbersome to discover in GitHub. They should be easily processable automatically instead...
I developed 6 years in X++ (Microsoft Dynamics AX) which doesn't have `null` and I missed it very seldom.
You might have a look at https://github.com/bwu-dart/bwu_polymer_routing but the one example I built yet uses hashes too, I guess that changing the navigation links (to not using hashes) should be...