Hey all, I like the pipelining syntax, but I often encounter the problem that one has to write code like this: rand(10) |> x -> filter(<=(0.5), x) I see that map, filter, accumulate, findfirst etc. all take a minimum of two arguments. If I define Base.filter(f::Function) = a -> filter(f,a) the a…

Because that already has a meaning, so changing that would be breaking: julia> foo() = println("hello") foo (generic function with 1 method) julia> map(foo) hello If you’re wondering how you can reach that, you can splat an empty container: julia> map(foo, []...) hello

Define map, filter, ... also as functionals

Internals & Design

ludwig-austermann September 17, 2022, 1:54pm 4

But why not add the simple behaviour case to the standard library?

1 Like

Topic		Replies	Views
Why are there no curried versions of map & filter? New to Julia	5	1152	September 29, 2020
Why no single argument `filter(f::function)`? Internals & Design	8	643	January 21, 2023
ANN: Transducers.jl, efficient and composable algorithms for map- and reduce-like operations Package Announcements	24	5478	March 25, 2019
Why no Base.Iterators.map? Internals & Design	12	3684	June 18, 2020
Function chaining with \|> and filter function General Usage question , piping	5	3708	November 1, 2018

Define map, filter, ... also as functionals

Related topics