refactor: Simpler merging mechanism #33

glen · 2022-07-29T04:41:43Z

glen commented

2022-07-29 04:41:43 +00:00

Merging of Pocomath modules is eased by allowing one PocomathInstance to
be merged into another. That allows types, for example, to be exported
as a PocomathInstance (so there is no need for a special identifier
convention for types; they can be directly added with an installType
method). Also, larger modules can just be exported as an instance, since
there is more flexibility and more checking in merging PocomathInstances
than raw modules.

Resolves #29.

Merging of Pocomath modules is eased by allowing one PocomathInstance to be merged into another. That allows types, for example, to be exported as a PocomathInstance (so there is no need for a special identifier convention for types; they can be directly added with an installType method). Also, larger modules can just be exported as an instance, since there is more flexibility and more checking in merging PocomathInstances than raw modules. Resolves #29.

glen added 1 commit 2022-07-29 04:41:43 +00:00

refactor: Simpler merging mechanism d9d7af961f

Merging of Pocomath modules is eased by allowing one PocomathInstance to
  be merged into another. That allows types, for example, to be exported
  as a PocomathInstance (so there is no need for a special identifier
  convention for types; they can be directly added with an installType
  method). Also, larger modules can just be exported as an instance, since
  there is more flexibility and more checking in merging PocomathInstances
  than raw modules.

glen merged commit 31d3be277d into main

2022-07-29 04:42:05 +00:00

glen referenced this issue from a commit

2022-07-29 04:42:05 +00:00

Merge pull request 'refactor: Simpler merging mechanism' (#33) from merge_instances into main

Sign in to join this conversation.

No reviewers