30 Nov
2017
30 Nov
'17
9:25 p.m.
My point is to have a class with public interface identical to typing.Generic, but without all runtime overhead. It's based on the assumption that few developers benefit with typing.Generic addition during production application execution. Those who do, can subclass typing.Generic directly.
On Nov 30, 2017, at 1:22 PM, Ivan Levkivskyi
wrote: FWIW, with PEP 560 generic classes will stay generic at runtime. I am not sure what you mean by this, but practically all existing runtime APIs (with few exceptions, see PEP 560) for generics will stay.