This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author shreyanavigyan
Recipients christian.heimes, erlendaasland, petr.viktorin, shreyanavigyan
Date 2021-05-20.14:57:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1621522622.87.0.104938503526.issue44099@roundup.psfhosted.org>
In-reply-to
Content
Yes. It's becoming hard to implement both static and heap types using one struct member. Since this is all about implementing a helping hand when it comes to types I think two different members one for static and another one for heap would be fine. And if someone then comes up with even a better idea, then I'll implement that. I'm now working on implementing them.
History
Date User Action Args
2021-05-20 14:57:02shreyanavigyansetrecipients: + shreyanavigyan, christian.heimes, petr.viktorin, erlendaasland
2021-05-20 14:57:02shreyanavigyansetmessageid: <1621522622.87.0.104938503526.issue44099@roundup.psfhosted.org>
2021-05-20 14:57:02shreyanavigyanlinkissue44099 messages
2021-05-20 14:57:02shreyanavigyancreate