Sequence of a stateful transducer is producing the wrong answer

Description

I'm producing more than one element on the 1-arity of the transducer, and sequence is only considering the last one.

Here is the transducer and the tests that fail for sequence:

Environment

OSX 10.10.3, java 1.8.0-ea-b124

Activity

Show:
David Nolen
April 26, 2015, 10:04 AM

Please demonstrate the problem without core.async. Thanks.

import
April 27, 2015, 1:32 AM

Comment made by: lucascs

Hi,

the last test I posted on the ticket, fails in cljs, but not in clj:

David Nolen
April 27, 2015, 1:43 PM

I've removed the core.async bits from the description to clarify the issue.

David Nolen
May 10, 2015, 8:40 PM

The implementation of sliding-window above does not appear to be correct, it doesn't return the result. This ticket needs more information.

import
May 10, 2015, 9:51 PM

Comment made by: lucascs

As I said on http://dev.clojure.org/jira/browse/CLJS-1222?focusedCommentId=38620&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-38620

changing the 1-arity of the sliding-window to that fixes the transducer.

The point of this ticket now is that the behavior of the same (wrong) transducer in clj (both core.async and sequence) and cljs (core.async) is different than cljs sequence.

Assignee

Unassigned

Reporter

import

Labels

Approval

None

Patch

None

Fix versions

Affects versions

Priority

Minor