Declare implementations and dependencies via standard interfaces for operations #8

glen · 2023-01-22T01:34:21Z

glen commented

2023-01-22 01:34:21 +00:00

Adds a new subdirectory interfaces where standard interfaces
are defined. Additional interfaces for a given operation can
be added with an AliasOf type operator. Provides type
operators that give the return type, full function type, and
the type of a dependency on, a given operator.

Resolves #6.

Adds a new subdirectory `interfaces` where standard interfaces are defined. Additional interfaces for a given operation can be added with an `AliasOf` type operator. Provides type operators that give the return type, full function type, and the type of a dependency on, a given operator. Resolves #6.

glen added 20 commits 2023-01-22 01:34:22 +00:00

1eb73be2fa refactor: entirely new scheme for specifying return types

d55776655f refactor: Convenience type operator for specifying concrete signatures

fbec410c42 feat: Implement complex arithmetic through sqrt

Together with any auxiliary functions needed for that goal. Also
  strives to ensure the same functions are being defined for
  number and for `Complex<T>`.

8c06c8f36e feat: Add generic operation `square` and numeric `unequal` (#4 )

Co-authored-by: Jos de Jong <wjosdejong@gmail.com>
Co-authored-by: Glen Whitney <glen@studioinfinity.org>
Reviewed-on: #4

cbd1719227 experiment: convert all implementations to plain types

04024a2a8d fix a TS issue

60ce6212b4 convert code to type aliases

a5848125e4 fix and test absquare for quaternion

74e2aef524 refactor: tighter universal interface types

072b2a1f79 refactor: Streamline publishing operations

Avoids clumsy naming properties by making the names the keys in
  an interface to which the signatures of all operations must be
  published. This also reduces the number of different symbols and
  avoids long lists of imports in the modules implementing multiple
  operations, which were redundant with the list of functions
  exported from such modules.

6d63d23498 refactor: Streamline types and signature specfications

The main mechanism for simplification was simply to assume that
  ZeroType<T> and OneType<T> will always be in T. That removed a lot
  of specialized typing, and presumably will be true in practice.

  Otherwise, removes extraneous type definitions and adds/clarifies
  a number of comments to hopefully make the scheme as clear as possible.

63c2d448c1 docs: describe how to run the prototype

a0b21181e6 chore: rename `OpType` to `Signature`

1b9d6b6428 chore: use direct function definitions instead of `{ params, returns }`

d147d0a576 chore: implement `AliasOf`

0ea786dcc2 chore: show how to inject multiple instances of the same function (WIP)

e468ec72dd chore: rephrase two todo's

bd05dc9267 chore: make SignatureKey generic instead of using unknown

637e339b17 refactor: clarify implementation names in sqrt