Re: [Pharo-users] [Moose-dev] Design Challenge: metrics missing value...

Yes I see. I will keep thinking about it. On Wed, 21 Dec 2016 20:58:26 +0100, Tudor Girba wrote: Hi, On Dec 21, 2016, at 3:05 PM, stepharong wrote: Hi Alex, Following the design proposed by Stef, in your case you would use a different

Re: [Pharo-users] [Moose-dev] Design Challenge: metrics missing value...

Hi, > On Dec 21, 2016, at 3:05 PM, stepharong wrote: > > > >> Hi Alex, >> >> Following the design proposed by Stef, in your case you would use a >> different collection. > > Doru I have multiple missingValue so that they embed their own strategy. > Now I do not know for

Re: [Pharo-users] [Moose-dev] Design Challenge: metrics missing value...

On Wed, 21 Dec 2016 12:05:32 +0100, Tudor Girba wrote: Hi, I forgot to mention that another option I played with was to always use a metric object, and never numbers. So, numberOfLinesOfCode would return a MetricValue. I think the same idea is present in

Re: [Pharo-users] [Moose-dev] Design Challenge: metrics missing value...

Hi Alex, Following the design proposed by Stef, in your case you would use a different collection. Doru I have multiple missingValue so that they embed their own strategy. Now I do not know for the scenario of alex. Cheers, Doru On Dec 21, 2016, at 8:13 AM, Alexandre Bergel

Re: [Pharo-users] [Moose-dev] Design Challenge: metrics missing value...

On Wed, 21 Dec 2016 08:13:19 +0100, Alexandre Bergel wrote: Hi Stef, You are raising an interesting point to discuss. This MissingValue is indeed better than having -1 Something to keep in mind: it may be that one would like to focus on the missing value and not

Re: [Pharo-users] [Moose-dev] Design Challenge: metrics missing value...

On Wed, 21 Dec 2016 08:07:39 +0100, Tudor Girba wrote: Hi, MissingValue (or NoValue) is definitely the way to go. The UniformOrderedCollection is an interesting idea, too. We had a NoValue like solution a long time ago but we discarded because we missed the idea

Re: [Pharo-users] [Moose-dev] Design Challenge: metrics missing value...

Hi Alex, Following the design proposed by Stef, in your case you would use a different collection. Cheers, Doru > On Dec 21, 2016, at 8:13 AM, Alexandre Bergel wrote: > > Hi Stef, > > You are raising an interesting point to discuss. This MissingValue is indeed >

Re: [Pharo-users] [Moose-dev] Design Challenge: metrics missing value...

Hi Stef, You are raising an interesting point to discuss. This MissingValue is indeed better than having -1 Something to keep in mind: it may be that one would like to focus on the missing value and not really the value. Consider: > testCollect > > | uarray collected | > uarray

Re: [Pharo-users] [Moose-dev] Design Challenge: metrics missing value...

Hi, MissingValue (or NoValue) is definitely the way to go. The UniformOrderedCollection is an interesting idea, too. We had a NoValue like solution a long time ago but we discarded because we missed the idea around collections. It would be really cool to have this working. Cheers, Doru > On

Re: [Pharo-users] [Moose-dev] Design Challenge: metrics missing value...

So basically you are trying to deal with missing values in collections. People working with R or Python data analytics framework made some ways to work with specific data structures called dataframes where you can have some missing values. For example you may have a look here: