stuartmorgan-g

> We already have an alternative i.e. to lay down the if-else such that it checks for web first. How is that an alternative to using `Platform` checks? The rest...

> Usually you would want the federated plugin implementations to be unlisted anyways. They are, but people can still get to the pub pages for them. And in some cases...

Yes, it's trivial. From my original post above: > I propose, as with #992, that this be skipped for packages with the `implements` keyword. (Also, I believe pub *already* detects...

> The description length requirement originates from SEO guidelines. Regardless of the origin, the effect is the packages are getting points deducted for no useful reason. I understand that there's...

> Why not just write: > > > macOS implementation of the platform interface for url_launcher plugin. That is a worse description; the exact mechanics of federated implementations are not...

> If I cast from `num?` to `int`, it maybe be because I know something But it may also be that that you meant to cast `num` to `int` and...

> I'm generally concerned about `as`, since it allows anything. Yes, that's why my preferred solution would be https://github.com/dart-lang/language/issues/1547. That didn't go anywhere though, and if we're going to be...

Yes, that lint time helps; someone mentioned it offline after I filed this. I would still argue that it's worth considering a new operator though, since having the cast operator...

Thanks for the discussion; feel free to close if it's not something you feel is worthwhile. I do want to address a couple of small points though: > We have...

> I don't understand how adding a new operator makes the migrations any more safe if it doesn't stop you from using the old one. I agree it doesn't help...