Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Add Successfulness types #119

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Conversation

brentleyjones
Copy link
Member

Unlike #71, this just adds the types needed to support success checking. Therefore it doesn't complete #59, since it needs some additional support at the ExpressionType level. Though, if you change ExpressionProbabilityMass to ProbabilityMass<OutcomeWithSuccessfulness<Int>> you can start to see where this is heading.

Features

  • Successfulness, a type that represents how many successes and failures an expression has.
    • Tests
    • Playground
  • OutcomeWithSuccessfulness, a way to represent successfulness with ProbabilityMass.
    • Tests
    • Playground

@brentleyjones
Copy link
Member Author

@JonathanHoffman Would you mind adding playground support for this? It would help prove it out more by having someone else look at it from the API point of view. Also, I love your playground pages. If not I will, just wondering if you would want to.

@brentleyjones
Copy link
Member Author

@JonathanHoffman This got lost with the holiday. Are you planning on doing the playground pages, or should I assign this back to myself?

`Successfulness` can represent the actual number of successes and failures that occurred while evaluating an `ExpressionType`, or it can represent the possibility of successes and failures in the context of a `FrequencyDistribution`.
A paired `FrequencyDistributionOutcomeType` and `Successfulness` Useful for determining the successfulness of expressions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant