Skip to content

Commit

Permalink
Merge branch 'main' of github.com:propensive/probably
Browse files Browse the repository at this point in the history
  • Loading branch information
propensive committed Jun 5, 2024
2 parents de8e418 + 8d18e0d commit 618a237
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
Binary file modified doc/images/1000x1000.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified doc/images/2400x2400@300dpi.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 1 addition & 1 deletion fury
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ project probably
module coverage
compiler scala
sources src/coverage
include gossamer/core dendrology/core digression/core
include gossamer/core dendrology/tree digression/core

module test
compiler scala
Expand Down
6 changes: 3 additions & 3 deletions readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -208,7 +208,7 @@ defined inside other test suites, making it possible to organise tests into a hi

## Status

Probably is classified as __maturescent__. For reference, Scala One projects are
Probably is classified as __maturescent__. For reference, Soundness projects are
categorized into one of the following five stability levels:

- _embryonic_: for experimental or demonstrative purposes only, without any guarantees of longevity
Expand All @@ -222,7 +222,7 @@ as long as caution is taken to avoid a mismatch between the project's stability
level and the required stability and maintainability of your own project.

Probably is designed to be _small_. Its entire source code currently consists
of 795 lines of code.
of 787 lines of code.

## Building

Expand Down Expand Up @@ -291,7 +291,7 @@ OÜ](https://propensive.com/).

The name _Probably_ acknowledges an appropriate level of confidence in writing tests which _probe_ the functionality of a program, in contrast to using types which (in theory, at least) _prove_ it.

In general, Scala One project names are always chosen with some rationale,
In general, Soundness project names are always chosen with some rationale,
however it is usually frivolous. Each name is chosen for more for its
_uniqueness_ and _intrigue_ than its concision or catchiness, and there is no
bias towards names with positive or "nice" meanings—since many of the libraries
Expand Down

0 comments on commit 618a237

Please sign in to comment.