You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To find the score, two columns (namely the params x and y in ppscore.score()) need to be supplied in call to score().
It would be nice to have a functionality where the user can get an array of results corresponding to all columns in a single line of code.
For instance, if comparisons between columns 'A', 'B', 'C', and 'D' are to be made, it should be possible to do so with a single line of code. Results could be obtained as a list of comparisons between A-B, A-C, A-D, B-C, B-D, and C-D.
Possible Solution
This can be achieved in two ways -
create another function which iterates over all possible combinations and yields/returns a list
add logic to existing implementation of score for the same.
Regarding test cases, it'd be easier to write a new one for a new function (as per 1), rather than modifying the existing implementation.
The text was updated successfully, but these errors were encountered:
roshnet
changed the title
feat: Return result for all possiible combintation of columns
feat: Return result for all possible combintations of columns
Apr 30, 2020
Feature Request 🎉
Description
To find the score, two columns (namely the params
x
andy
inppscore.score()
) need to be supplied in call toscore()
.It would be nice to have a functionality where the user can get an array of results corresponding to all columns in a single line of code.
For instance, if comparisons between columns 'A', 'B', 'C', and 'D' are to be made, it should be possible to do so with a single line of code. Results could be obtained as a list of comparisons between
A-B
,A-C
,A-D
,B-C
,B-D
, andC-D
.Possible Solution
This can be achieved in two ways -
score
for the same.Regarding test cases, it'd be easier to write a new one for a new function (as per 1), rather than modifying the existing implementation.
Remarks
@8080labs I'd like to work on it.
The text was updated successfully, but these errors were encountered: