c-boun...@haskell.org] On
| Behalf Of Simon Marlow
| Sent: 21 July 2009 09:05
| To: Isaac Dupree
| Cc: cvs-ghc@haskell.org
| Subject: Re: SrcLoc/SrcSpan/Located naming
|
| We're at the stage where the GHC API is beginning to settle down a bit,
| so it might be a good idea to keep backwards compa
Dupree
| Cc: cvs-ghc@haskell.org
| Subject: Re: SrcLoc/SrcSpan/Located naming
|
| We're at the stage where the GHC API is beginning to settle down a bit,
| so it might be a good idea to keep backwards compatibility where
| possible. If we rename things, we can leave the old names in, but
| DE
We're at the stage where the GHC API is beginning to settle down a bit,
so it might be a good idea to keep backwards compatibility where
possible. If we rename things, we can leave the old names in, but
DEPRECATED, for one release.
Cheers,
Simon
On 20/07/2009 19:51, Isaac Dupree wrot
Do we make any attempt to keep the GHC API consistent between major
releases, or is the policy generally just to make any naming changes
that we find fitting for GHC's purposes?
-Isaac
Thomas Schilling wrote:
I think the inconsistencies are mostly because SrcSpan was added
later. Patches to
I think the inconsistencies are mostly because SrcSpan was added
later. Patches to improve the problematic cases would (most likely)
be welcome.
2009/7/20 Isaac Dupree :
> is a confusing mess!
> The most important module is named SrcLoc, which is acceptable.
> It contains three types,
> SrcLoc,
>
is a confusing mess!
The most important module is named SrcLoc, which is acceptable.
It contains three types,
SrcLoc,
SrcSpan, which approximately is two SrcLocs (begin and end),
and Located, which combines a SrcSpan (not a SrcLoc!) with an arbitrary
other type.
In practice (well, in my case at
