antirez 66f9393ee4 Fix setTypeNext call assuming NULL can be passed.
Segfault introduced during a refactoring / warning suppression a few
commits away. This particular call assumed that it is safe to pass NULL
to the object pointer argument when we are sure the set has a given
encoding. This can't be assumed and is now guaranteed to segfault
because of the new API of setTypeNext().
2015-03-31 15:26:35 +02:00
..
2012-04-13 17:52:33 -07:00
2014-09-29 06:49:07 -04:00
2014-08-08 10:43:54 +02:00
2015-01-19 14:10:12 -05:00
2015-03-30 12:17:46 +02:00
2014-12-14 12:25:42 +02:00
2015-03-04 11:48:19 -08:00
2014-07-02 17:04:14 +02:00
2014-08-08 14:54:02 +02:00
2015-02-17 11:33:08 -05:00
2014-08-08 10:05:32 +02:00
2015-01-19 14:10:12 -05:00
2015-02-03 15:42:56 +01:00
2014-07-02 16:31:22 +02:00
2011-07-06 15:22:00 +02:00
2015-01-02 11:16:08 -05:00
2015-01-02 11:16:08 -05:00