Conversation
|
@dnfield, @jonahwilliams: any thoughts on the failures here? |
|
Part of the reason this ends up being breaking is that we have inadvertently created scenarios where our matrices are non-invertible. It's also not clear whether turning this on will effect users as well, as it might end up being a large breaking change. We would need to:
I don't think it will be obvious to most users what the problem is if this assert starts firing in their application, so we should be careful. |
|
@Hixie, @goderbauer: assuming this is not an easy call to make and in the interest of not blocking an analyzer roll could we consider adding a comment and:
? |
|
Since the assert is functionally diasbled we can comment it out here to unblock analyzer |
|
Awesome. Thanks @jonahwilliams ! |
|
Was a bug filed to fix this? We should fix this soon; adding commented-out code is strictly against our style guide. |
Description
Fixes an assert that was bogus.
Flagged by the newly updated
unrelated_type_equality_checkslint in this failing try:https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket.appspot.com/8915275287386529616/+/steps/analyze_flutter/0/stdout
Cheers @srawlins for the fix!
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?