diff options
author | Stephen Dolan <mu@netsoc.tcd.ie> | 2012-09-16 11:07:36 +0100 |
---|---|---|
committer | Stephen Dolan <mu@netsoc.tcd.ie> | 2012-09-16 11:07:36 +0100 |
commit | cc2fb20ca03ca0cd30c0d9c768ead9b8cb7130f9 (patch) | |
tree | ae35533814dc408b0ceb529e70b35706c3c600d0 | |
parent | df195b31873010f18883446c6e0e629a594badc5 (diff) |
Hrm. Update operators (//=, +=, etc.) aren't very well thought out.
In complex cases, their behaviour is kinda weird. Here's a failing
test for what I think they should do.
-rw-r--r-- | c/testdata | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -312,9 +312,10 @@ def inc(x): x |= .+1; inc(.[].a) [{"foo":[1,2], "bar": 42}, {"foo":[1], "bar": null}, {"foo":[null,false,3], "bar": 18}, {"foo":[], "bar":42}, {"foo": [null,false,null], "bar": 41}] [[1,2], [1], [3], [42], [41]] -.[] //= 42 -["hello",true,false,[false],null] -["hello",true,42,[false],42] +# FIXME: behaviour of update operators +# .[] //= .[0] +# ["hello",true,false,[false],null] +# ["hello",true,"hello",[false],"hello"] .[] | [.[0] and .[1], .[0] or .[1]] [[true,[]], [false,1], [42,null], [null,false]] |