Vectors and seqs (including lists) are sequential

Maps and sets are not

But all are seqable

So for example when json encoding you might encode everything sequential by emitting [ then using seq to walk the thing emitting each item, then followed by ]

I am not positing that Sequential is the same as ISeq. I'm positing that there is no example that shows Sequential is different from Seqable. Other than that if you defined something that was Sequential and not Seqable, you might end up with an exception in RT.seq.

Well, that is an example, maps are seqable but not sequential

Sequential means something has an order that is part of the interface of the thing

You are correct. I overstated what I'm looking for. I agree you can be Seqable and not Sequential. I'm looking for something that is Sequential but not Seqable. In other words, for some reason for Sequential to exist.

I agree that Sequential means that. But operationally, I cannot find a place in the Java code where it makes a difference. It does occur to me just now that I did not look in the Clojure source.

https://git.sr.ht/~hiredman/lions/tree/master/item/src/com/manigfeald/json.clj#L15 so here is some code that does what I said about using sequential to determine what should be encoded as a json array

Seqability is not sufficient there, because maps are seqable but should not be encoded that way

Also, strings are seqable? but not sequential?

Okay, thanks. I finally get it. I'm a little slow on the uptake been sitting here too long already today. By testing for map? first the code has already filtered out likely all Seqable-not-Sequential types and sequential? could be replaced by seqable?, but I'll definitely concede that the semantics are clearer this way, as well as allowing for other data types in the future. Thanks for an example from real life (so-called).

Yeah, and sequential? there could be vector? or seq? with little real world difference

> By testing for map? first the code has already filtered out likely all Seqable-not-Sequential types and sequential? Not so, sets are another builtin type that are Seqable, but not Sequential. Additionally, these interfaces are open for extension, so you can make your own and the library can still handle those cases. For example, https://github.com/achim/multiset/blob/master/src/main/multiset/core.clj

data.json does more like what you describe, but as a protocol, maps(associative collections) get the object writer and other java.util.Collections get the array writer

Doesn't map call seq on its collection argument? Semantics aside, I'm back to the case where if this function got a Sequential that wasn't Seqable, it would blow up in RT.seq.

Sorry, crossed paths with multiple responses. I'll concede that there must be situation where there is something that is Sequential and not Seqable and never makes it to RT.seq.

even if it is always the case that things that are Sequential are always processed by seqing, that doesn't mean they are equivalent

just like you might take an iterator over a map and a list, but want to do different things with the items you get by running the iterator based on the type of the source collection

I do concede the semantic difference. I was thinking purely operationally from current code. Thank you both for the clarifying this for me.