On Thursday, August 18, 2016 at 10:52:42 AM UTC-7, Michael Borregaard wrote: > > That sounds right. I wonder if this is not a bug? >
>From my reading of the all the related issues, it is a known "issue" ;) It looks like a good solution is being ironed out. But I don't think this will be added to the 0.5.x timeline, but rather be a 0.6.x feature (along with a lot of other amazing .() features!). For your example you can use the workaround at the moment that map deals with this case in the expected manner: map(x->is(x, "b"), ["a", "b"]) will give the array answer (though likely not what you wanted ...) Gabriel
