ramsestom
ramsestom
> > So, if I want to get rid of this error, I have to test if my targetZ value is null or not before calling the pixelsToWorld function without...
> @ramsestom wrote: > > > Giving a function "nothing" (aka null) should always be the same as not giving the function anything. > > I just don't buy this....
> But the automatic conversion of null into non-null is logically inconsistent. Can't disagree more. In the case where the parameter has a default value, any `null` value should be...
> @ramsestom: see [this example](https://github.com/dart-lang/language/issues/156#issuecomment-459186639). > Generally, the whole NNBD endeavor in dart is about specifically prohibiting the interpretation you are advocating for. I saw you exemple but in my...
> It's not about the typo. You can use the correct spelling and still get null accidentally - because the corresponding entry in the map was not assigned, but you...
@munificent I am only talking about the case where the optional parameter is non-nullable and you call the function with a `null` value for this parameter. So I only consider...
Prior to NNBD, Dart was automatically giving a `null` optional parameter its default value. So ```dart foo([String optional = "default") { print(optional); } main() { foo(null)); } ``` would print...
It is really usefull when you want to parse or output to json a larger structure that contains a GeoJsonObject. The JsonSerializableGenerator from the json_serializable package (https://github.com/dart-lang/json_serializable) relly on these...
I can't agree more with @insinfo . I think the reason why threads where not implemented into Dart in the first place is because Dart was mainly focused into compiling...
> Most of the time copying is really really cheap compared to the actual computation and shared memory isn't worth the headache. Also don't think thread synchronization comes for free!...