Changes between Version 31 and Version 32 of Holes


Ignore:
Timestamp:
May 4, 2012 10:35:48 PM (2 years ago)
Author:
simonpj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Holes

    v31 v32  
    150150  * Requires evaluation semantics for hole 
    151151 
    152 '''SLPJ'''.  I'm really not sure what you mean by "must have the same type.  For example 
     152'''SLPJ question'''.  I'm really not sure what you mean by "must have the same type.  For example 
    153153{{{ 
    154154f xs = _?p : xs 
     
    162162If we generalise `f` then NOTHING can have the same type as the hole.  But it would be very strange not to generalise `f` (and `g`).   
    163163 
    164 It seems much simpler to me either to have anonymous holes, or to let the user give them names, but to pay no attention to the name except to display them in error messages, so that user can say "oh, that hole" rather than having to look at the exact source location. '''End of SLPJ''' 
     164It seems much simpler to me either to have anonymous holes, or to let the user give them names, but to pay no attention to the name except to display them in error messages, so that user can say "oh, that hole" rather than having to look at the exact source location. '''End of SLPJ question''' 
    165165 
    166166=== Term brackets (ranges) ===