7 Jan
2010
7 Jan
'10
11:15 a.m.
On Thu, Jan 07, 2010 at 04:00:31PM +0100, Bas van Dijk wrote:
As I explained in my announcement of 'safer-file-handles', I discovered a serious lack of expressive power in my 'regions' package. I have now solved that problem in the way I envisaged by removing the 'resource' parameter from 'RegionT' and using existential quantification to bring the 'resource' type back at the place I need it but hidden from the outside.
But if I understand correctly, now you can't know from the type signature what kind of resource a given code accesses. Isn't this a drawback? Wouldn't it be better to write something like TopRegion (File `And` Network) to tell something needs both? Cheers! -- Felipe.