ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergi Vladykin <sergi.vlady...@gmail.com>
Subject Re: Deprecate GridFunc
Date Fri, 01 Apr 2016 15:27:47 GMT
+1

I think it is a good idea to mark GridFunc and F with @Depricated
annotation and encourage developers to refactor the code which uses them
when they come across it. This way we'll gradually get rid of this "true
functional programming" stuff.

Sergi

2016-04-01 12:46 GMT+03:00 Vladimir Ozerov <vozerov@gridgain.com>:

> Yakov,
>
> This is very hard to reason whether it is affect performance or no. There
> are lots of "views" on critical paths (cache, IO, discovery, affinity), and
> their semantics is virtually unpredictable. Not to say about additional GC
> pressure.
>
> Anyway, looks like we have consensus that this class should be avoided.
>
> Vladimir.
>
> On Fri, Apr 1, 2016 at 12:36 PM, Yakov Zhdanov <yzhdanov@apache.org>
> wrote:
>
> > +1,
> >
> > However, personally I try not to accept new code on reviews relying on
> F. I
> > don't think we have any usages of mentioned methods on critical paths
> that
> > may affect performance. So, for now I would ask reviewers to very
> carefully
> > accept new code using F.
> >
> > --Yakov
> >
> > 2016-04-01 10:41 GMT+03:00 endianignite <endianignite@gmail.com>:
> >
> > > Wow, that really is an infamous class.  Yikes.  +1 from me for
> deprecate
> > &
> > > refactor.
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Deprecate-GridFunc-tp8214p8217.html
> > > Sent from the Apache Ignite Developers mailing list archive at
> > Nabble.com.
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message