> I particularly like Yehuda Katz's explanation on why it works this
> way: https://github.com/yarnpkg/yarn/issues/838#issuecomment-253362537
This was a powerful description for me. @Rob thank you for
providing that!
1. The articulation of the purpose/philosophy behind the whole thing
was re
> Whether "pinning" is the right word is a different debate, but when we
> view pinning as a workflow-focused feature, versus the specification
> in the manifest (which is the "requirement"), then I think the
> connotation actually works fairly well (e.g., a pinboard is something
> you pin to while
> What is your evaluation of the proposal?
Negative.
The “Motivation” logic seems incongruent possibly even contradictory.
The where syntax is cited as “… rarely used, [and] hard to discover ….”
while simultaneously a source of confusion to new developers. Taking
both statements together this pro
On Tue, Jun 14, 2016, at 01:37 PM, Xiaodi Wu via swift-evolution wrote:
> On Tue, Jun 14, 2016 at 12:16 PM, David Waite solutions.com> wrote:
>> I’m a bit late to this conversation, and I don’t totally understand
>> the goal.
>>
>> There are a *lot* of things you can do in for…in loop with pattern
@Xiaodi Wu a couple of times you've said things were "explicit"
this or that.
>* Swift is explicitly a C-family language. In most or all other C-
>family languages, for loop statements allow specification of
>conditions for exiting the loop but not for filtering. Therefore,
>Swift's use of `where
On Fri, Jun 10, 2016, at 11:49 AM, Erica Sadun via swift-evolution wrote:
>
>> On Jun 10, 2016, at 9:24 AM, Erica Sadun
>> wrote:
>>
>>
>>> On Jun 10, 2016, at 9:22 AM, Erica Sadun via swift-evolution >> evolut...@swift.org> wrote:
>>>
>>>
On Jun 10, 2016, at 8:02 AM, Xiaodi Wu via swift-evol
On Thu, May 26, 2016, at 02:26 AM, David Hart via swift-evolution wrote:
> I believe it also helps readability. Associated type are part of the
> declaration and I think it's worth pursuing better readability than
> programmer friendliness at the declaration. When reading a type
> declaration that
On Mon, May 16, 2016, at 11:18 AM, Chris Lattner via swift-evolution
wrote:
> Hi Everyone,
>
> As we get deeper into the Swift 3 release cycle, we’re beginning to have
> a more precise understanding about what the release will shape up to be.
> Ted posted details of the Swift 3 release process la
> SE-0066 is a very narrow proposal - it only affects syntax, not
> semantics. The type system semantics that you seem interested in are
> unlikely to happen regardless of the syntax changes SE-0066 imply, and
> SE-0066 doesn’t have anything to do with that.
It is most disappointing to read thes
