What if you wanted to use a package outside of the platform? If a
platform package depends on it you have to use the version that came
with the platform, otherwise you get diamond dependency issues.
Therefore, if one of the platform packages depends on a package with a
less stable API you, in prac
* Mark Lentczner [2013-01-23 19:35:25-0800]
> I'm with Chris on this: Once you've included it, it's in. That is - people
> will code against those packages - because, well, there they are! "levels
> of warranty" as listed on some web page aren't really going to imply much!
What is bad, exactly, a
I'm with Chris on this: Once you've included it, it's in. That is - people
will code against those packages - because, well, there they are! "levels
of warranty" as listed on some web page aren't really going to imply much!
So, I think if a package is included, all it's dependencies need to be
inc
The point is not that one shouldn't use these packages. After all, you
could as well install them from hackage if you needed them.
The point is that these packages do not come with the same "warranty" as
the platform packages. Many people do not care (and it's fine), but
for those who care (e.g. p
I am very skeptical that we could maintain this distinction for very long,
Leading quite quickly to confusion. How realistic is it to expect punters
(like me) to not make use of of these packages in the platform; they would
de facto be in the platform Within a release or two, whether we liked it
or
Another possibility worth to consider is to ship these packages together
with the platform without advertising them as "platform" packages.
For these packages we'd make no claims that their API is good or stable,
or that these packages even will be present in the future platform releases.
If we co
Hi Greg,
On Wed, Jan 23, 2013 at 9:43 AM, Gregory Collins
wrote:
> Hopefully you've noticed the proposal I made this morning for attoparsec to
> join the list of platform packages. I wanted to bring up a matter for
> discussion before I propose more packages for inclusion. I'd very much like
> fo
Hi all,
Hopefully you've noticed the proposal I made this morning for attoparsec to
join the list of platform packages. I wanted to bring up a matter for
discussion before I propose more packages for inclusion. I'd very much like
for the following packages written by Bryan to make it into the plat