[Python-Dev] Missing *-unpacking generalizations (issue 2292)
Benjamin Peterson
benjamin at python.org
Sat Mar 21 21:57:22 CET 2015
More information about the Python-Dev mailing list
Sat Mar 21 21:57:22 CET 2015
- Previous message (by thread): [Python-Dev] Missing *-unpacking generalizations (issue 2292)
- Next message (by thread): [Python-Dev] Fwd: class os.DirEntry is confusing,
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Mar 20, 2015, at 19:16, Neil Girdhar wrote: > Wow, this is an excellent review. Thank you. > > My only question is with respect to this: > > I think there ought to be two opcodes; one for unpacking maps in > function calls and another for literals. The whole function location > thing is rather hideous. > > What are the two opcodes? BUILD_MAP_UNPACK and > BUILD_MAP_UNPACK_WITH_CALL? > > The first takes (n) a number of maps that it will merge, and the second > does the same but also accepts (function_call_location) for the purpose > of > error reporting? Exactly.
- Previous message (by thread): [Python-Dev] Missing *-unpacking generalizations (issue 2292)
- Next message (by thread): [Python-Dev] Fwd: class os.DirEntry is confusing,
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list