mv-python
mv-python
> Maybe call it `get_container_type()` and make it available for all Cython types, returning `None` if not a typed container ? The same applies to typed C++ containers, for example....
There are still open points to be implemented but I decided to put it already as ready for review...
PR now is I think feature complete. There are two main points pending: * support of tuples (`tuple[int, long, float]`, `tuple[int, ...]`) * support of inferring through container methods (`.keys()`...
I will be bold here and scheduled it for 3.3 release. I think this PR is not introducing anything controversial which should block it although there there will be some...
The PR is not handling following case: ``` a: int = 5 a: int a = 6 ```
This PR will break users which redeclare variable with same type.
Yes it seems that mypy supports variable redeclaring but only when configured to do so [1]. I think an error is reasonable way for it in Cython. [1] https://github.com/python/mypy/pull/6197
> but it also seems a risky last minute change. I suggested it as late change just because: 1. it is isolated change, the change is located in separate if...
OK I refactor the code based on feedback: * I used `.is_subscript()` instead of `isinstance()` test * I split the cases into separate branches * I fixed the case of...
> Why doesn't the call to IndexNode.analyse_as_type() (or SliceIndexNode.analyse_as_type() respectively) return a MemoryViewSliceType then ? Why does the transform have to do the expression analysis here? The rationale for approach...