darcs

Patch 2168 remove MonadProgress which is never actually used anyw...

Title remove MonadProgress which is never actually used anyw...
Superseder Nosy List bfrk
Related Issues
Status accepted Assigned To
Milestone

Created on 2021-05-09.11:54:28 by bfrk, last changed 2021-05-15.17:17:39 by ganesh.

Files
File name Status Uploaded Type Edit Remove
patch-preview.txt bfrk, 2021-05-09.11:54:27 text/x-darcs-patch
remove-monadprogress-which-is-never-actually-used-anywhere.dpatch bfrk, 2021-05-09.11:54:27 application/x-darcs-patch
unnamed bfrk, 2021-05-09.11:54:27 text/plain
See mailing list archives for discussion on individual patches.
Messages
msg22760 (view) Author: bfrk Date: 2021-05-09.11:54:27
For discussion. IMO the idea of tracking/reporting progress of patch
application as a monadic effect is sound in principle. This is better than
doing it with unsafePerformIO as in Darcs.Patch.Progress. The
D.P.MonadProgress module has "Copyright (C) 2011 Ganesh Sittampalam",
perhaps you can elaborate how you imagined it to be used?

1 patch for repository http://darcs.net/screened:

patch a48704373c77fcde756098536f43449ac8843e1c
Author: Ben Franksen <ben.franksen@online.de>
Date:   Sun May  9 14:03:07 CEST 2021
  * remove MonadProgress which is never actually used anywhere
Attachments
msg22761 (view) Author: ganesh Date: 2021-05-10.06:56:55
On 09/05/2021 12:54, Ben Franksen wrote:
> 
> New submission from Ben Franksen <ben.franksen@online.de>:
> 
> For discussion. IMO the idea of tracking/reporting progress of patch
> application as a monadic effect is sound in principle. This is better than
> doing it with unsafePerformIO as in Darcs.Patch.Progress. The
> D.P.MonadProgress module has "Copyright (C) 2011 Ganesh Sittampalam",
> perhaps you can elaborate how you imagined it to be used?

I'm afraid I don't remember much directly.

Looking in the 'darcs annotate' of the file, it was introduced by this
patch:

> 1: patch fa605983659dd1c4942bbe09b1954e2b8008ce11
> Author: Ganesh Sittampalam <ganesh@earth.li>
> Date:   Mon Apr  4 18:45:41 GMT Summer Time 2011
>   * generalise type of applyPatches using a new MonadProgress class

And there it looks like I was just abstracting/moving some code that was
already in applyPatches at the time. That function eventually seems to
have ended up in D.R.ApplyPatches.applyPatches which in turn isn't
actually used any more.

I don't exactly know why I did it. I might have had some vision in mind
of mocking it in future. I vaguely recall that around that time I had a
grand plan to abstract all our IO code around type classes so it was
clear what side-effects different code could run, but it never happened.

I doubt it's worth keeping for the sake of it.
msg22778 (view) Author: ganesh Date: 2021-05-15.14:54:35
Looks fine.
History
Date User Action Args
2021-05-09 11:54:28bfrkcreate
2021-05-10 06:56:57ganeshsetmessages: + msg22761
2021-05-10 13:43:31bfrksetstatus: needs-screening -> needs-review
2021-05-15 14:54:35ganeshsetstatus: needs-review -> accepted-pending-tests
messages: + msg22778
2021-05-15 17:17:39ganeshsetstatus: accepted-pending-tests -> accepted