Leaf Petersen

> Question 2:  you seem to be leaning towards the use of "inout" as a synonym of "exact", but I have difficulty understanding the reasoning leading from "inout" to "exact"....

> I find the _word_ `inout` confusing. It's difficult to see how this word may carry the meaning of "exact". Ah, sorry, I misunderstood your question. Here's the intution: -...

@tatumizer I think this is getting a bit far afield - variance is definitely a confusing subject, but I don't think we're going to fix that here. Is it fair...

@Hixie Just to be sure we're on the same page: Kotlin has two different kinds of variance - this kind (declaration-site) which is what C# uses, and which I don't...

cc @mit-mit @lrhn @eernstg @munificent @stereotype441 @natebosch @jakemac53 @rakudrama @srujzs @sigmundch @rileyporter

If we made the `Type` type generic, then you could write `if (T is Type)` with no special casing. Not very intuitive though.

> I'm not sure if I like the idea having this added to Dart because the beauty of Dart is its simplicity. The fact that it isn't as concise as...

> * treat the argument expression as a static getter or method call on the referenced type. If the referenced type is not in scope at the call site is...

Per the question around FutureOr, [this issue](https://github.com/dart-lang/language/issues/433) might be relevant. Per the question around trivial bounds: Currently `class Foo { T get something => ...}` is useful because it means...

Transferring this to the dartdoc repo, since as best I can tell this isn't a language issue.