Jukka and Ivan will be visiting the Bay Area in September and we'd like to organize another meetup. Here are the proposed (tentative) logistics:
Date: Friday, Sept. 20
Time: 1pm - 5pm
Location: Facebook in Menlo Park (building and room TBD)
So far Ivan, Jukka, Guido, Rebecca, Martin (?), and myself have committed to attending. I'm also volunteering the rest of the Pyre team.
Please let us know in advance if you plan on attending so that we can book an adequately sized room.
Also now's the time to think about topics to discuss or presentations you want to give.
I want to announce the submission of a new typing PEP, for ParameterSpecifications (https://github.com/python/peps/pull/1259). We discussed this concept at the last typing summit (presentation can be found here https://github.com/facebook/pyre-check/blob/master/docs/Variadic_Type_Varia…), and there seemed to be general consensus on the utility of this idea, and the appropriateness of the particular solution.
One note that I know there was some disagreement on was the name for the feature itself, with some folks preferring ArgSpec. I wrote up a brief note in the PEP itself why we're not as big fans of that name, but I'd love to hear all of your opinions on this issue, as well as on anything else in the PEP.
When PCs or laptops based on the Intel microprocessor run a Microsoft Windows operating system, we generically refer to such architectures as Wintel. People who work in such environments by supporting users and resolving their issues are Wintel Engineers.
These engineers configure and install all server hardware, including the Windows OS and products procured from third-parties, onto the systems. They build, configure, assess, and recommend hardware and software.
They should possess above average analytical and fixing skills. Engineers own and run an issue with minimal intervention from others ensuring all relevant parties are informed on time.
More info : https://www.fieldengineer.com/skills/wintel-engineer
I personally prefer shorter to type names, so ArgsSpec looks better in my eyes.
Concatenate and ListVariadic seems satisfactory for positional arguments.
You know, Python supports positional-only, keyword-only, *args and
Could ArgsSpec (or ParameterSpecifications) be extended to explicitly
provide these kinds of parameters explicitly?
Another thing is the default argument.
The exact value of the default is not significant for typing but a
flag of the default value presence is important.
Can ArgsSpec provide this information?