[英]Are Clojure transducers the same concept as intermediate operations on streams in Java?
當我在 Clojure 中學習轉換器時,我突然想起了它們讓我想起的東西:Java 8 流!
Clojure:
(def xf
(comp
(filter odd?)
(map inc)
(take 5)))
(println
(transduce xf + (range 100))) ; => 30
(println
(into [] xf (range 100))) ; => [2 4 6 8 10]
爪哇:
// Purposely using Function and boxed primitive streams (instead of
// UnaryOperator<LongStream>) in order to keep it general.
Function<Stream<Long>, Stream<Long>> xf =
s -> s.filter(n -> n % 2L == 1L)
.map(n -> n + 1L)
.limit(5L);
System.out.println(
xf.apply(LongStream.range(0L, 100L).boxed())
.reduce(0L, Math::addExact)); // => 30
System.out.println(
xf.apply(LongStream.range(0L, 100L).boxed())
.collect(Collectors.toList())); // => [2, 4, 6, 8, 10]
除了靜態/動態類型的差異外,這些在目的和用法上似乎與我非常相似。
與 Java 流轉換的類比是否是考慮轉換器的合理方式? 如果不是,它是如何有缺陷的,或者兩者在概念上有何不同(更不用說實現了)?
主要區別在於,動詞(操作)集在某種程度上對流關閉,而對轉換器開放:例如嘗試在流上實現partition
,感覺有點二等:
import java.util.function.Function;
import java.util.function.Supplier;
import java.util.stream.Stream;
import java.util.stream.Stream.Builder;
public class StreamUtils {
static <T> Stream<T> delay(final Supplier<Stream<T>> thunk) {
return Stream.of((Object) null).flatMap(x -> thunk.get());
}
static class Partitioner<T> implements Function<T, Stream<Stream<T>>> {
final Function<T, ?> f;
Object prev;
Builder<T> sb;
public Partitioner(Function<T, ?> f) {
this.f = f;
}
public Stream<Stream<T>> apply(T t) {
Object tag = f.apply(t);
if (sb != null && prev.equals(tag)) {
sb.accept(t);
return Stream.empty();
}
Stream<Stream<T>> partition = sb == null ? Stream.empty() : Stream.of(sb.build());
sb = Stream.builder();
sb.accept(t);
prev = tag;
return partition;
}
Stream<Stream<T>> flush() {
return sb == null ? Stream.empty() : Stream.of(sb.build());
}
}
static <T> Stream<Stream<T>> partitionBy(Stream<T> in, Function<T, ?> f) {
Partitioner<T> partitioner = new Partitioner<>(f);
return Stream.concat(in.flatMap(partitioner), delay(() -> partitioner.flush()));
}
}
也像序列和減速器一樣,當您轉換時,您不會創建“更大”的計算,而是創建一個“更大”的源。
為了能夠通過計算,你已經推出了xf
從流至流的功能,以提升操作從方法到一流的實體(以解開他們從源頭)。 通過這樣做,您已經創建了一個轉換器,盡管接口太大。
以下是將任何(clojure)轉換器應用於流的上述代碼的更通用版本:
import java.util.function.Function;
import java.util.function.Supplier;
import java.util.stream.Stream;
import java.util.stream.Stream.Builder;
import clojure.lang.AFn;
import clojure.lang.IFn;
import clojure.lang.Reduced;
public class StreamUtils {
static <T> Stream<T> delay(final Supplier<Stream<T>> thunk) {
return Stream.of((Object) null).flatMap(x -> thunk.get());
}
static class Transducer implements Function {
IFn rf;
public Transducer(IFn xf) {
rf = (IFn) xf.invoke(new AFn() {
public Object invoke(Object acc) {
return acc;
}
public Object invoke(Object acc, Object item) {
((Builder<Object>) acc).accept(item);
return acc;
}
});
}
public Stream<?> apply(Object t) {
if (rf == null) return Stream.empty();
Object ret = rf.invoke(Stream.builder(), t);
if (ret instanceof Reduced) {
Reduced red = (Reduced) ret;
Builder<?> sb = (Builder<?>) red.deref();
return Stream.concat(sb.build(), flush());
}
return ((Builder<?>) ret).build();
}
Stream<?> flush() {
if (rf == null) return Stream.empty();
Builder<?> sb = (Builder<?>) rf.invoke(Stream.builder());
rf = null;
return sb.build();
}
}
static <T> Stream<?> withTransducer(Stream<T> in, IFn xf) {
Transducer transducer = new Transducer(xf);
return Stream.concat(in.flatMap(transducer), delay(() -> transducer.flush()));
}
}
我看到的另一個重要區別是 Clojure Transducers 是可組合的。 我經常遇到這樣的情況,我的流管道比您的示例中的要長一些,其中只有一些中間步驟可以在其他地方重用,例如:
someStream
.map(...)
.filter(...)
.map(...) // <- gee, there are at least two other
.filter(...) // <- pipelines where I could use the functionality
.map(...) // <- of just these three steps!
.filter(...)
.collect(...)
我還沒有找到一種理智的方法來實現這一目標。 我希望我擁有的是這樣的:
Transducer<Integer,String> smallTransducer = s -> s.map(...); // usable in a stream Integer -> String
Transducer<String,MyClass> otherTransducer = s -> s.filter(...).map(...); // stream String -> MyClass
Transducer<Integer,MyClass> combinedTransducer = smallTransducer.then(otherTransducer); // compose transducers, to get an Integer -> MyClass transducer
然后像這樣使用它:
someStream
.map(...)
.filter(...)
.transduce(smallTransducer)
.transduce(otherTransducer)
.filter(...)
.collect(...)
// or
someStream
.map(...)
.filter(...)
.transduce(combinedTransducer)
.filter(...)
.collect(...)
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.