[swift-evolution] [Review] SE-0111: Remove type system significance of function argument labels

[L. Mihalkovic]

An interesting take on arg label/name, granted this is including destructuring of obj literals (so one level down from the method sig, but which is not without analogy to what could be done to tuples with named fields). The main point of comparison is what the type of f1 and f2 are. 

This is in typescript, where the signatures ultimately have to translate down to javascript where everything maps to 
f(p,q,r,s,t) {
  var p1 = arguments.0; // is p or this
   ...
}
last week i was back to writing lots of ts 1.8 code and i find the type system incredibly precise and flexible (P|Q... yeah)

// Type of f1 is (arg?: { x?: number, y?: number }) => void 
function f1({ x = 0, y = 0 } = {}) { } 

// And can be called as: 
f1(); 
f1({}); 
f1({ x: 1 }); 
f1({ y: 1 }); 
f1({ x: 1, y: 1 }); 

// Type of f2 is (arg?: (x: number, y?: number) => void 
function f2({ x, y = 0 } = { x: 0 }) { } 
f2(); 
f2({});                 // Error, x not optional 
f2({ x: 1 }); 
f2({ y: 1 });          // Error, x not optional 
f2({ x: 1, y: 1 });

Regards
(From mobile)

> On Jun 30, 2016, at 8:26 PM, Chris Lattner via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Hello Swift community,
> 
> The review of "SE-0111: Remove type system significance of function argument labels" begins now and runs through July 4. The proposal is available here:
> 
>    https://github.com/apple/swift-evolution/blob/master/proposals/0111-remove-arg-label-type-significance.md
> 
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
> 
>    https://lists.swift.org/mailman/listinfo/swift-evolution
> 
> or, if you would like to keep your feedback private, directly to the review manager.
> 
> What goes into a review?
> 
> The goal of the review process is to improve the proposal under review through constructive criticism and contribute to the direction of Swift. When writing your review, here are some questions you might want to answer in your review:
> 
>    * What is your evaluation of the proposal?
>    * Is the problem being addressed significant enough to warrant a change to Swift?
>    * Does this proposal fit well with the feel and direction of Swift?
>    * If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
>    * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
> 
> More information about the Swift evolution process is available at
> 
>    https://github.com/apple/swift-evolution/blob/master/process.md
> 
> Thank you,
> 
> -Chris Lattner
> Review Manager
> 
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160704/eafac5db/attachment.html>