Skip to content

[FEATURE] Evaluate code reconciliation at zero cost (no branching at runtime, no extra memory usage, ...) between repositories #2008

@jerome-benoit

Description

@jerome-benoit

Duplicate issue

  • I've searched for any related issues and avoided creating a duplicate issue.

Description

Proposals:

  • Monorepo with:
    • poolifier -> @poolifier/node
    • poolififer-web-worker -> @poolifier/web

Or

  • Build zero cost abstraction allowing code reconciliation. The design pattern in that PR poolifier/poolifier-web-worker@b958569 allowing different runtime support at no performance cost is probably a starting point permitting to merge poolifier and poolifier-web-worker code back into the same code base.
    There's still open issues like worker_threads and web worker Worker, EventEmitter and EventTarget, ... zero cost abstraction on different APIs: the encapsulation needed to expose an union of the classes signature will hardly be a zero cost abstraction.

Attachments

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions