The reason for the braces in type families is because type indices are treated differently than normal parameters. I don't think this should be adopted for type synonyms either.<br><br>Cheers,<br>hugo<br><br><div class="gmail_quote">
On Thu, Mar 27, 2008 at 9:48 PM, Wolfgang Jeltsch <<a href="mailto:g9ks157k@acme.softbase.org">g9ks157k@acme.softbase.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Am Donnerstag, 27. März 2008 22:43 schrieb Wolfgang Jeltsch:<br>
<div class="Ih2E3d">> Am Mittwoch, 26. März 2008 03:07 schrieb Hugo Pacheco:<br>
> > > The extra syntax has its advantages (more local information) and<br>
> > > disadvantages (more clutter). We weren't convinced that we need the<br>
> > > extra syntax, so left it out for the moment. However, this is<br>
> > > something that can always be changed if experience shows that programs<br>
> > > are easier to understand with extra syntax. It doesn't affect the<br>
> > > type theory and is really a pure language design question. I'd be<br>
> > > glad to hear some more opinions about this matter.<br>
> ><br>
> > I would go for the braces as Claus suggested,<br>
><br>
> I would do so, too.<br>
<br>
</div>Hmm, but then we should also introduce braces for ordinary type synonyms:<br>
<br>
type ReaderWriterT m = ReaderT (WriterT m)<br>
<br>
x :: {ReaderWriterT IO} Char<br>
<br>
> […]<br>
<div><div></div><div class="Wj3C7c"><br>
Best wishes,<br>
Wolfgang<br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</div></div></blockquote></div><br>