Closed jorisbontje closed 5 years ago
Yeah, #10 has some outstanding things that need to be done though.
As a workaround you can compile with --laxStrings:on
.
It's --nilseqs:on
.
Ahh yes. Sorry, my bad.
On Fri, 28 Sep 2018, 00:31 Andreas Rumpf, notifications@github.com wrote:
It's --nilseqs:on.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nim-lang/redis/issues/14#issuecomment-425348292, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPDe8Nlnga-wfvhhRtlUDFeoD2zL4Phks5ufdBKgaJpZM4W8_Wa .
Any update? It seems that there is no working solution for Nim to use redis properly right now. https://github.com/xmonader/nim-redisclient crashes the compiler even!
nilseqs is not an option all my code is aware of not nil seqs and strings... :cry:
@sinkingsugar not much we can do except get #10 in shape. If you could help out that would be great :)
Should be fixed now.
With nim v0.19.0:
My understanding is that this might already be addressed by PR #10