Sam Zhou

Namespaces are not properly loaded for me, and I see the same error messages.

In between the assert and the use of `a.x`, there can be some code that sets `a.x` to be `None` again. Precisely deciding whether to invalidate the refinement will make...

@alxclark This is not actively maintained. I only touched the code to upgrade Flow internally. We have since stopped the sync between internal and external repo for this project. (There...

Looking at [this](https://circleci.canny.io/cloud-feature-requests/p/support-new-m1-arm-based-macs), it looks like ARM mac is coming soon from CircleCI.

Yes, you might see that we already started to build it on mac arm: https://app.circleci.com/pipelines/github/facebook/flow/5541/workflows/ed21b666-0e64-435f-88ca-1f1623ed0c51/jobs/97719

Expected behavior, since $Keys are designed to model Object.keys

I can understand why that's happening, but I agree that the error message is certainly not good.

This issue is caused by Flow's existing unsoundness wrt literals, where they exist in a superposition state of being a literal and being a more general type, which causes bug...

Yeah the root cause is the same. When we are unable to pick an overload, we might get these bad error messages.

Do you mind if I reopen this issue? I think this is a valuable discussion to have. This year we have started converging with TS where it makes sense. e.g....