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.

Sign up for GitHub

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

Jump to bottom

Establish consistent construction terminology #215

Open

propensive opened this issue Mar 7, 2025 · 1 comment

Assignees

Owner

propensive commented Mar 7, 2025

We need to build various different things using Soundness APIs. A variety of terms are used for the building process:

build
construct
make
create
and probably others.

The building process may also has several nuances:

side-effecting operations involved with the creation (e.g. establishing a file on disk)
allocation of an object
subsequent or previous operations, often on a mutable value, which help to specify the process
parsing or other processing
the potential for exceptions to be thrown

We should audit the current uses of these terms across all libraries, and make them consistent.

The text was updated successfully, but these errors were encountered:

propensive self-assigned this

Owner Author

propensive commented Mar 7, 2025

Definitions:

make
- Abacist
- Anticipation
- Capricious
- Charisma
- Escapade
- Galilei
- Hellenism
- Kaleidoscope
- Octogenarian
- Panopticon
- Polyvinyl
- Probably
- Serpentine
- Telekinesis
create
- Acyclicity
- Galilei
- Rudiments
build
- Gossamer
- Nomenclature
- Polyvinyl
construct
- Anticipation
- Gossamer
- Quantitative
- Wisteria

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment