-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to Data.Text
#15
Comments
The original work was done by @MassiveTactical. We also merged in some other changes. We agree on using Text although I see both sides. Using UTF16 instead of UTF8 was also hotly debated in the .net world. In the end we don't think the overhead is high enough to use something else in place of Text especially since the only thing left in our code base using something other than Text is protocol-buffers. |
It seems pretty official that we are stuck with UTF16 Text for our Haskell code. I vote for the switch. |
Any movement on this? I can create a pull request if needed. |
This driver is probably looking for a new maintainer now, not more pull requests :) |
I (or better we, here at selectel) can maintain it ;) |
great! Tony is no longer at 10gen, and I don't know how to contact him. The contact is now supposed to be Steve Francia. I sent a message to him. If I don't hear back I can go to 10gen office hours on Thursday 24. |
Well, maybe we should create a community, maintained fork? |
10gen likes the idea. Please start on your fork and they should give it official approval soon. |
@gregwebs It has been two weeks, should I contact 10gen myself to check if everything is allright? |
The community fork is now released to Hackage with the blessing of 10gen |
Hello, have you considered switching to
text
fromcompact-string
, since the latter is now obsolete (according to the Hackage page)?Good thing is @alphaHeavy has is done in his fork!
The text was updated successfully, but these errors were encountered: