Cross reference https://github.com/JuliaLang/julia/pull/10211#issuecomment-110471886
On Tue, Jun 9, 2015 at 1:20 PM, andrew cooke <[email protected]> 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? I don't understand your concern here. AFAIK, `|>` has always been a function (operator) and it still is. The operator is not being deprecated, only the "overload"/method of it that pipe command together is deprecated. This has nothing to do with the parser and is same with any other method deprecation. You can still define whatever method on the operator and it should still work. > > andrew > > On Tuesday, 9 June 2015 14:11:35 UTC-3, Yichao Yu wrote: >> >> On 2015年6月9日 星期二 10:00:23, andrew cooke <[email protected]> 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
