Watiko wrote:
> Problem:
> call assert_false(1)
> then we expected v:errors is
> [" line 0: Expected False but got 1"]
> but actual value is
> [" line 0: Expected False but got 1"]
Thanks. Although best way is to not let the function fail :-).
--
God made the integers; all else is the work
Thank you for follow-up, Tony.
>with an unexpected space at the very start but only one space between
>1 and but, and none after 2.
Yes, I knew that such behavior. And I also think the leading space is
unecpected.
additional patch:
diff --git src/eval.c src/eval.c
index 81dc478..fd2f74c 10064
The same double space applies to assert_true() but not to
assert_equal(), for instance:
:let v:errors = []
:call assert_equal(1,2)
:echo v:errors
[' line 0: expected 1 but got 2']
with an unexpected space at the very start but only one space between
1 and but, and none after 2.
IMHO this whole qu
Hi, lists.
Problem:
call assert_false(1)
then we expected v:errors is
[" line 0: Expected False but got 1"]
but actual value is
[" line 0: Expected False but got 1"]
diff --git src/eval.c src/eval.c
index 2668f3d..81dc478 100644
--- src/eval.c
+++ src/eval.c
@@ -9183,10 +9183,13 @@ fill_assert_e
