| c n a |
c := #{ 'b' -> 1. 'a' -> 2. 'c' -> 3. 'd' -> -4 }.
n := #{ 'new' -> 'N' }.
a := #{ 'b' -> 1. 'a' -> 2. 'c' -> 3. 'd' -> -4. 'new' -> 'N' }.
TestCase new assert: n, c equals: a
it failed. But when I run tests in Amber, it's all green. 😢
Issue on test runner: #1248.
It seems I actually do test it:
https://lolg.it/amber/amber/src/master/lang/src/Kernel-Tests.st#L1005
I am very puzzled about why all Amber tests pass.
When I tried to recreate it in workspace
```
| c n a |
c := #{ 'b' -> 1. 'a' -> 2. 'c' -> 3. 'd' -> -4 }.
n := #{ 'new' -> 'N' }.
a := #{ 'b' -> 1. 'a' -> 2. 'c' -> 3. 'd' -> -4. 'new' -> 'N' }.
TestCase new assert: n, c equals: a
```
it failed. But when I run tests in Amber, it's all green. 😢
Issue on test runner: #1248.
These codes produce false.
It is because
=
is order-dependent: implemented asself associations = anAssociativeCollection associations
.Two tests:
and
and a method:
What do you think?
It seems I actually do test it:
https://lolg.it/amber/amber/src/master/lang/src/Kernel-Tests.st#L1005
I am very puzzled about why all Amber tests pass.
When I tried to recreate it in workspace
it failed. But when I run tests in Amber, it's all green. 😢
Issue on test runner: #1248.
I added fixed comma tests in master.
asSet
can be expensive operation, evenat:
. Thinking how to shortcut that...As
and:
is also a little bit expensive (not inlined yet), as well as non-local return (try-catch handler), sticking toifFalse:
. Added this: