Ian Jeffries

Quick experience report: I've been doing Concur (well `concur-replica`) programming for about a month now, and the scenario described in this issue was becoming a very serious problem. If I...

A few more thoughts: ### Making sure I understand the problem One of the most enjoyable things about Concur to me is having local state at the leaves. Imagine in...

Is your problem that you'd like to be able to autorun the tests no matter what warnings there are? If so the `--warning` flag of `ghcid` will let you do...

Thanks for the thoughts, this is going on my todo list.

Make an initial experimental repo: Here are manual lenses: https://github.com/seagreen/microlens-th-experiments/blob/master/plain-lenses/src/Experiment.hs#L121 Here are th lenses: https://github.com/seagreen/microlens-th-experiments/blob/master/th-lenses/src/Experiment.hs#L122 And here are the results: https://github.com/seagreen/microlens-th-experiments/blob/master/results.txt The test sources are the most boring thing I...

PS `bench` was a great recommendation.

Here are my results with `-L 300`. The difference between manual and TH lenses stayed small. ``` benchmarking cd ~/code/mine/microlens-th-experiments/small-data; rm -rf ./.stack-work; stack build time 2.688 s (2.677 s...

Began work on this upstream: https://github.com/pkamenarsky/replica/pull/18

Random idea: it might be cool to have a reference implementation of `concur-core` that only cares about correctness and readability, not speed, so we could use it to check where...

This would definitely be cool. One idea for a place to start would be to put a simple multiplayer game in the examples. Snake is a classic for this.