`each` macro improper behavior? about janet HOT 8 CLOSED

@pepe Just in case, I did just now try that. There is no difference if one calls (:flush stdout) directly after pp in the second implementation.

from janet.

Thanks. TBH, I just woke up and saw the combination of print and order :-), so my suggestion went.

from janet.

I haven't really thought much about the details here, but I've submitted #1402 anyway.

FWIW, I did run some more tests across some of my repositories and those didn't turn up anything.

from janet.

Fixed in #1402.

from janet.

Have you tried to flush stdout after pp?

from janet.

FWIW, make test doesn't show errors for:

diff --git a/src/boot/boot.janet b/src/boot/boot.janet
index 46fcabae..e3b5ee9e 100644
--- a/src/boot/boot.janet
+++ b/src/boot/boot.janet
@@ -442,8 +442,8 @@
               :each ~(,in ,ds ,k)
               :keys k
               :pairs ~[,k (,in ,ds ,k)]))
-         (set ,k (,next ,ds ,k))
-         ,;body))))
+         ,;body
+         (set ,k (,next ,ds ,k))))))
 
 (defn- iterate-template
   [binding expr body]

from janet.

@sogaiu If that works with make test and works with the second example of lines-from-buf from the original post in this thread, it'd be awesome if you submitted the PR to get that change.

from janet.

@llmII Perhaps this issue can be closed?

from janet.