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 pablogsal
Recipients BTaskaya, gvanrossum, lys.nikolaou, pablogsal, rhettinger
Date 2020-09-08.20:52:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1599598322.05.0.688205116215.issue41746@roundup.psfhosted.org>
In-reply-to
Content
> Let me know if I'm misunderstanding the proposal.  Are you proposing a non-standard ASDL extension to that won't work with existing ASDL parsers? 

No, I am not proposing any modification to the ASDL parsers nor the ASDL definition language.

I am proposing a modification to the internal data structures we use internally to carry sequences of ASDL types. Currently, asdl_seq is a type that holds an array of void* pointers and the user is supposed to cast the individual items to the correct types, which is error prone. I am proposing to add a new field to our internal structures that allows the user to have some certainty over what these sequences contain.
History
Date User Action Args
2020-09-08 20:52:02pablogsalsetrecipients: + pablogsal, gvanrossum, rhettinger, lys.nikolaou, BTaskaya
2020-09-08 20:52:02pablogsalsetmessageid: <1599598322.05.0.688205116215.issue41746@roundup.psfhosted.org>
2020-09-08 20:52:02pablogsallinkissue41746 messages
2020-09-08 20:52:01pablogsalcreate