Re: [Snowdrift-dev] Mechanism

2016-08-10 Thread Bryan Richter
On Tue, Aug 09, 2016 at 01:35:55PM -0600, Peter Harpending wrote: > Hi, everyone, > > I wrote a mechanism library a few months ago, which I don't believe > was ever merged into the main code tree. Then, I had summer classes, > and several deaths in my family, so I haven't been paying much >

Re: [Snowdrift-dev] Mechanism implementation

2016-03-20 Thread Bryan Richter
On Tue, Mar 15, 2016 at 12:50:00AM -0600, Peter Harpending wrote: > I need to go to bed, but tomorrow, I'll try to work on gluing the > mechanism to the rest of Snowdrift. I would hold off on doing this, or at least run your plan past me first. It involves core architecture decisions. Thanks!

Re: [Snowdrift-dev] Mechanism implementation

2016-03-19 Thread Bryan Richter
On Tue, Mar 15, 2016 at 09:13:53AM -0600, Peter Harpending wrote: > On 03/15/2016 12:50 AM, Peter Harpending wrote: > > code that requires one to use the feature, so I vote that > > Silly me, I forgot to mention how I vote. I vote that we leave it for > now, because it's unlikely to cause any

Re: [Snowdrift-dev] Mechanism implementation

2016-03-14 Thread Peter Harpending
On 03/14/2016 05:10 PM, Bryan Richter wrote: > 1. I'm not sure the Eq instances of MechPatron and MechProject are > sound. As defined, `==` is the moral equivalent of checking that the > two values cannot both exist in the database at the same time > (database uniqueness), but that's not quite