Message326078
| Author | thautwarm |
|---|---|
| Recipients | benjamin.peterson, brett.cannon, gvanrossum, nascheme, ncoghlan, serhiy.storchaka, thautwarm, vstinner, yselivanov |
| Date | 2018-09-22.05:40:07 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1537594807.49.0.956365154283.issue32892@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I'm in favor of this idea for prospective extensions that could be implemented through this brand-new ast.Constant. Actually I used to expect a more general ast.Constant when I was manipulating ASTs half a year ago, at that time my job is to make staging functions that take some user-defined types as constants(in these scenes, these types are definitely immutable and permanent) to gain performance improvements and avoid redundant allocations, and what I exactly wanted is such an ast.Constant. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-09-22 05:40:07 | thautwarm | set | recipients: + thautwarm, gvanrossum, brett.cannon, nascheme, ncoghlan, vstinner, benjamin.peterson, serhiy.storchaka, yselivanov |
| 2018-09-22 05:40:07 | thautwarm | set | messageid: <1537594807.49.0.956365154283.issue32892@psf.upfronthosting.co.za> |
| 2018-09-22 05:40:07 | thautwarm | link | issue32892 messages |
| 2018-09-22 05:40:07 | thautwarm | create | |