On Sat, Mar 12, 2016 at 05:08:42PM -0700, Peter Harpending wrote: > Hello, all, > > I've got 95% of an implementation of the mechanism (see > <https://snowdrift.coop/p/snowdrift/w/en/mechanism> if you don't > know what I'm talking about). You can clone the git repository from > <https://gitlab.com/pharpend/sd-mech.git>. To build/run it, follow > the instructions in the README.
This is amazing. I have a ton of things going on elsewhere in the Development role to get this site going. Peter, I am provisionally putting you in charge of the mechanism. The most I'll ask of you is to make sure your library fits into the architecture when the time comes to do so. I'll provide coding feedback when I can get the time, but until then I encourage you to keep making progress!! Everyone else, feel free to work with Peter on this! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ok, doing a quick review now, after all: 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 the same thing as being the same value. 2. Control.Error <3 3. I don't think the concept of a suspended patron is necessary yet. I could be misremembering, but I'm pretty sure one is either a patron or one is not. 4. > context "100 years of chaos" $ do Yes, perfect. 5. > he = it I get it, but it provides very little compared to the damage it could cause. 6. The stuff I wrote for doing tests against a database was intended to be abstracted out into a standalone library. I'll still do that. I guess you had to rewrite it to be able to use HSpec, though, so *shrug* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Thanks again! Hooray progress.
signature.asc
Description: Digital signature
_______________________________________________ Dev mailing list [email protected] https://lists.snowdrift.coop/mailman/listinfo/dev
