DarthFubuMVC/bottles — comment on commit 107fdf9d8bf2627e5d63d6daf3ca2c85440aef04
File: src/Bottles/PackageFacility.cs line 18
By jeremydmiller:

So go with the += operator -- as has already been stated a couple times.

________________________________
From: Joshua Flanagan

To: Jeremy D. Miller
Sent: Thu, November 3, 2011 10:06:32 AM
Subject: Re: [bottles] changing confusing private property setter to use an
idiomatic function call (107fdf9)

I'll weigh in on Dru's side on this one. I cannot think of any example, in
any language, where an assignment operation does not replace the existing
value.
I get that it's a clever trick to make the syntax less noisy. But if it
requires a user to read the source to understand the intention, (and in
fact, to even know they don't understand the intention, since it looks like
something they do know) its probably not worth it.

On Thu, Nov 3, 2011 at 9:41 AM, Dru Sellers <
reply@reply.github.com>wrote:

> That's a fair point, I agree that this is the way that Dru Sellers does
> prefer it. But I will still stand by my statement that this way (method
> based) is clearer to a larger portion of the .Net community. I also believe
> that using an '=' sign when a '+' operation was occurring is a misleading
> operator choice. It can lead one to think you are 'replacing' the action
> rather than 'adding' to it.
>
> ---
> Reply to this email directly or view it on GitHub:
>
>https://github.com/DarthFubuMVC/bottles/commit/107fdf9d8bf2627e5d63d6daf3ca2c85440aef04#commitcomment-693064
>4
>

---
Reply to this email directly or view it on GitHub:
https://github.com/DarthFubuMVC/bottles/commit/107fdf9d8bf2627e5d63d6daf3ca2c85440aef04#commitcomment-693108