Replies: 4 comments 3 replies
-
This is the change (line 122) that broke these tests. The new propagation wasn't considered in the tests: 7a0ea40#diff-371895e22cf3ce93a5cf4d22a70c5171007a02e68679a267bf4436cd724e0a59 |
Beta Was this translation helpful? Give feedback.
-
Oh thanks for brining it up. It was quite an adventure to get type inference working, we had a couple back and forths and we should clean up the codebase. All relevant tests are executed from Tests that you point to seem to be testing dead code. I should delete it. Please let me know if you have further questions! |
Beta Was this translation helpful? Give feedback.
-
Surely we need more comments in type inference code :-) The failure is actually expected there, as "Very concrete" in this context means that it involves no type references. So the call should be done as IsFullyDefined(VeryConcreteType([TypeReference('Any')])) Example colab: https://colab.research.google.com/drive/1dD23lpksDPBc5UenT8HKqJEpv0v4U8PW?usp=sharing Let me know if you have further questions! |
Beta Was this translation helpful? Give feedback.
-
Oh, that's very interesting! I was thinking of implementing a C++ version, but didn't get to this. Asking questions here is great, as someone may have the same question later :-) But in case you have very narrow questions, you are welcome to ask them by email - I reached out to email that you have in your profile. |
Beta Was this translation helpful? Give feedback.
-
Hi there,
I'm reading through the various type inference modules to get a better understanding. I'm having trouble running the tests in types_graph_building_test.py and wanted to know if that's a bug on my side.
For example,
test_when_connection_with_other_predicates
fails because theexpected
case lists 3Equality
s, but theedges
result holds:Equality
s, andPredicateArgument
sOther tests in the same module fail for the same reason. All tests in
type_inference_test.py
on the other hand, succeed.See:
Beta Was this translation helpful? Give feedback.
All reactions