Skip to content
This repository has been archived by the owner on Dec 31, 2021. It is now read-only.

PEP584 #13

Open
orsinium opened this issue Apr 8, 2019 · 2 comments
Open

PEP584 #13

orsinium opened this issue Apr 8, 2019 · 2 comments

Comments

@orsinium
Copy link

orsinium commented Apr 8, 2019

Some of drafts quite promising. For example, PEP-584:

https://www.python.org/dev/peps/pep-0584/

This pep allows you to sum up dicts. It's exactly like creating new dict and executing update() on it. Probably, this pep will be rejected because sum for dicts isn't symmetric. Is it appropriate PEP for pepallow?

@ghost ghost self-assigned this Apr 8, 2019
@isidentical
Copy link
Collaborator

As i said in #11 . It is better to avoiding mutation of builtin functions / types. We tried to mutate None in PEP336 implementation and it doesnt look cool.

I am thinking about a branching Allow operations. For PEPs like 313, it is better to use AST but for peps like 584 we can use a runtime mutation strategy backed by ctypes

@isidentical-archive isidentical-archive deleted a comment Apr 8, 2019
@isidentical isidentical changed the title What about drafts? PEP584 Apr 8, 2019
@isidentical
Copy link
Collaborator

By the way, we dont have any problem about drafts / withdrawen peps.

@isidentical isidentical unassigned ghost Apr 8, 2019
@ghost ghost added Future MP and removed future labels Apr 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants