jairov4
Im getting the same error, during execution of third party code. I think that third party is using heavy reflection.
It looks super-important to me. This example suggest we can just forget keys on producer sides and only re-key on consumer via GroupBy. Is it having drawbacks?
still happening in 1.0.9 even I think it would be benefical for codegen to apply optimization
@codafyer I have added support for custom field and issue type scheme in #25 I hope it helps in the same direction
@illume I imagine thats related, however afaik pygame is not storing textures in vram so it do not need to asumme an special behavior. However, thanks for your workaround it...
@JukkaL > Value types are a great feature, thanks! This seems to address [mypyc/mypyc#841](https://github.com/mypyc/mypyc/issues/841) -- what do you think? > Yes, it goes in that direction, however the implementation presented...
makes sense, I didnt saw that NamedTuples can be subclassed and add new mutable members
@JukkaL can you review at this point. I think is ready due the tests I have made, let me know if you consider any other test.
@JukkaL Hey, I have made some modifications there. Including hiding it behind a feature flag. I can make the additional verification for the cases you mentioned in a new PR...