great, thanks.
On Tuesday, 9 June 2015 16:29:58 UTC-3, Stefan Karpinski wrote: > > There are no plans to drop |> from being parsed entirely – it's a useful > operator. There has been some talk about making it more than just an normal > infix operator: > > - https://github.com/JuliaLang/julia/issues/554 > - https://github.com/JuliaLang/julia/issues/5571 > - https://github.com/JuliaLang/julia/issues/11608 > > But there's far from consensus on that. I have no special knowledge of how > that discussion is going to turn out. > > > On Tue, Jun 9, 2015 at 1:20 PM, andrew cooke <and...@acooke.org > <javascript:>> wrote: > >> >> right, but things like that need special support in the language parser >> (i believe), so if the command is being dropped, maybe it is also being >> dropped form the parser? >> >> andrew >> >> On Tuesday, 9 June 2015 14:11:35 UTC-3, Yichao Yu wrote: >> >>> On 2015年6月9日 星期二 10:00:23, andrew cooke <julia...@googlegroups.com> >>> wrote: >>> > huh. and what exactly is deprecated? just the associated function, >>> or the >>> > symbol too? in the next version, will it still be possible to define >>> a >>> > meaning for |> ? >>> >>> The use of it to pipe commands together >>> https://github.com/JuliaLang/julia/blob/master/base/deprecated.jl#L205 >>> >>> > >>> > On Tuesday, 9 June 2015 13:26:05 UTC-3, Simon Frost wrote: >>> > > Dear All, >>> > > >>> > > I tried (and failed) to search for this, but I wanted to know why >>> the >>> > > forward pipe operator |> has been deprecated in favour of >>> pipe(...,...,)? >>> > > >>> > > Best wishes, >>> > > Simon >>> >> >
