feat: Runtime type reflection #17

glen · 2023-10-17T22:01:56Z

glen commented

2023-10-17 22:01:56 +00:00

Now each behavior specification "knows" its type information.
Also bumps version number and sets up so that the scripts will run on Windows as well as Unix (thanks to Jos).
Resolves #5.
Resolves #16.

Now each behavior specification "knows" its type information. Also bumps version number and sets up so that the scripts will run on Windows as well as Unix (thanks to Jos). Resolves #5. Resolves #16.

glen added 21 commits 2023-10-17 22:01:57 +00:00

feat: Precisely reflect the type of an implementation at runtime (!!) 770c302342

feat: Demonstrate a trick for further resolving the dep type at compiletime da5b2c3467

feat: Simplify the reflected type of an implementation af02f1cb29

feat: Demonstrate macros to encapsulate the type-reflection process 9eff2bc265

chore: Update to ts-macros@2.4.0 ae2303af7c

issue: ts-macros appears to be generating temp variable clashes dc6cf5165d

WIP: try to use ts-macros for more implementations 0e2a1e830a

chore: make pnpm go work cross platform 4947a80cb4

log the reflectedType of complex square root ce974e2a99

use ts-macros directly from Github until v2.4.2 is published on npm 20078d2c87

feat: convert sqrt for numbers 0ebaaf35ee

chore: use exact version numbers fd4ecd70ba

feate: implement a basic parser for the reflected types 1ca0ac42d0

chore: output the reflected types enclosed in quotes for clarity 2f7677c371

chore: upgrade to ts-macros@5.2.0 instead of directly from git 632c82966b

feat: do not generate export via macro but keep the export in TS for better DX 20236355c1

refactor: Possible alternate syntax for reflection 457b9cdc91

feat: Add reflecTypes that allows multiple reflections at once 49b1332917

refactor: Explore final patterns for runtime typing with ts-macros ebe7cf831e

The idea is to have a single macro which lets you reflect multiple
  implementations. That's provided in this commit. However, there
  is a hitch with implementations that have no dependencies: the
  reflectedType property did not exist on the Signature type. However,
  if you add it, then the Signature type becomes opaque, so we would
  have to look up signatures; but that appears to be tricky, as there
  doesn't seem to be a way to reflect the full generic type of the
  Signatures interface.

  So this commit provides three example resolutions:
  (A) Export a type RTT and all no-dependency implementations have to
      intersect with RTT (see 'add' in number/arithmetic.ts)
  (B) Write no-dependency implementations as functions of no arguments
      (representing no dependencies passed in) returning the actual
      implementation (see 'subtract' in number/arithmetic.ts)
  (C) Make a special DSignature<> generic type (short for "Direct Signature"
      used only (and always) for implementations with no dependencies, and
      a matching $Dreflect!() macro for generating their type info.

  Of course, there may be other possibilities I haven't thought of. But we
  need to pick one. I don't think it matters _too_ much, since there only
  a small fraction of all implementations have no dependencies.

refactor: Settle on making all implementations (possibly vacuous) factories d8199341e0

refactor: Extend reflection to all implementations so far 6f44567306

And also enhances the reflected type parsing so that the types of all
  implementations so far will parse.

glen merged commit 40146c2f48 into main

2023-10-17 22:02:18 +00:00

glen referenced this issue from a commit

2023-10-17 22:02:19 +00:00

feat: Runtime type reflection (#17)

josdejong commented

2023-10-18 12:18:26 +00:00

🎉

Sign in to join this conversation.

No reviewers

No Label

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: glen/typocomath#17