+1, both packages need it and should really just be using the same
implementation. Otherwise we'll just end up with conflicts when using sdl2
*and* OpenGL or we'll be juggling between two statevars implementations
imported qualified that really are the same thing.
On Wed, Oct 22, 2014 at 7:30 PM, Edward Kmett
We're currently actively working on writing better SDL 2 bindings in sdl2.
For various reasons, it can't depend on the OpenGL package directly, but it needs a state variable construction.
Sadly, not every platform with SDL 2 has OpenGL -- thanks Microsoft.
We'd like to depend on the StateVar package, but then we'll get two versions of the notion of a StateVar that conflict.
By *far* the cleanest option for us moving forward would be if OpenGL switched to using the externalStateVar package that you also maintain, then we could incur a dependency on that.
I realize that when this was last proposed there was some pushback from the Haskell Platform, but otherwise what we're going to start seeing is a profusion of almost-compatible APIs, which is the very thing that the Haskell Platform is meant to prevent.
This would necessitate adding StateVar to the Haskell Platform, as OpenGL is in the Haskell Platform.
The package is maintained by the same maintainer as the current OpenGL package.
Discussion Period: 2 weeks
-Edward Kmett
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
-- Alp Mestanogullari