Re: [Haskell-cafe] Diving into the records swamp (possible GSoC project)

2013-04-27 Thread AntC
> Johan Tibell gmail.com> writes: > > The discussions about an overhauled record system also involve lots of talk about record sub-typing, extensible records, and other more advanced features. I'd like to point out that there doesn't seem to be a great demand for these features. ... Sorry, Jo

Re: [Haskell-cafe] Diving into the records swamp (possible GSoC project)

2013-04-27 Thread AntC
> Johan Tibell gmail.com> writes: > > Instead of endorsing one of the listed proposals directly, I will emphasize the problem, so we don't lose sight of it. The problem people run into *in practice* and complain about in blog posts, on Google+, or privately when we chat about Haskell over beer

Re: [Haskell-cafe] Diving into the records swamp (possible GSoC project)

2013-04-27 Thread Adam Gundry
Hi Johan, On 26/04/13 20:46, Johan Tibell wrote: > Hi Adam, > > Since we have already had *very* long discussions on this topic, I'm > worried that I might open a can of worms be weighing in here, but the > issue is important enough to me that I will do so regardless. I'm the one busily opening

Re: [Haskell-cafe] Diving into the records swamp (possible GSoC project)

2013-04-27 Thread Adam Gundry
Hi Petr, On 26/04/13 19:53, Petr Pudlák wrote: > Hi Adam, > > very nice idea. As the others, I'm curious why you chose to implement > SORF in favor of the other ideas? As I've commented in a message just now [1], by mentioning SORF I didn't mean to exclude taking on board the other proposals (p

Re: [Haskell-cafe] Diving into the records swamp (possible GSoC project)

2013-04-27 Thread Adam Gundry
Hi AntC, Thanks for the feedback! On 26/04/13 09:55, AntC wrote: >> Adam Gundry strath.ac.uk> writes: >> >> Hi, >> >> I am hoping to do a GSoC project this year working on GHC, and >> have been pointed in the direction of the records issue (in >> particular, the desire to overload field names

Re: [Haskell-cafe] Diving into the records swamp (possible GSoC project)

2013-04-26 Thread Johan Tibell
Hi Adam, Since we have already had *very* long discussions on this topic, I'm worried that I might open a can of worms be weighing in here, but the issue is important enough to me that I will do so regardless. Instead of endorsing one of the listed proposals directly, I will emphasize the problem

Re: [Haskell-cafe] Diving into the records swamp (possible GSoC project)

2013-04-26 Thread Petr Pudlák
Hi Adam, very nice idea. As the others, I'm curious why you chose to implement SORF in favor of the other ideas? I just read the SORF proposal, and I'm a bit concerned about what error messages would GHC issue when someone would type incorrect code involving such records. Currently Haskell's erro

Re: [Haskell-cafe] Diving into the records swamp (possible GSoC project)

2013-04-26 Thread adam vogt
Hi Aleksandar, This library for extensible records does use -XDataKinds: . It doesn't have as many definitions as HList, but that might be because more recent extensions are more powerful. Many other libraries are listed

Re: [Haskell-cafe] Diving into the records swamp (possible GSoC project)

2013-04-26 Thread Aleksandar Dimitrov
Slightly, off-topic, but just because I've been spending my last couple of days trying to shoehorn an inheritance-based subytping type system into Haskell (without full OO-power, so no methods or mutable state.) > Oleg/Ralf's HList paper covers all the ground for first-class records. It > depends

Re: [Haskell-cafe] Diving into the records swamp (possible GSoC project)

2013-04-26 Thread AntC
> Adam Gundry strath.ac.uk> writes: > > Hi, > > I am hoping to do a GSoC project this year working on GHC, and have been > pointed in the direction of the records issue (in particular, the desire > to overload field names). Heck you're brave! Are you sure you want to step into the aggravated i

[Haskell-cafe] Diving into the records swamp (possible GSoC project)

2013-04-26 Thread Adam Gundry
Hi, I am hoping to do a GSoC project this year working on GHC, and have been pointed in the direction of the records issue (in particular, the desire to overload field names). This has been discussed on-and-off for years, and while there are lots of ideas [1], little has been implemented in GHC it