Skip to content

Redesign public hyperlight API #1560

Description

@ludfjig

This issue is meant to cover redesigning the public hyperlight API for a 1.0 release. It's separate from #765, because this one is referring to redesigning the existing API, while #765 is concerned about removing public items that should not be public.

Some things I can think of right now:

  • Remove Uninitiated sandbox and evolve
  • Combine and/or SandboxConfiguration and SandboxRuntimeConfig
  • Add builder-pattern where makes sense
  • Rename MultiUseSandbox (name is outdated)
  • Possibly add some light-weight type-safety to MultiUseSandbox to prevent host functions from being added (see feat(host): implement Registerable for MultiUseSandbox #1392)
  • Narrow method-specific errors and error variants, rather than a catch-all HyperlightError

Please add more!

Activity

  1. added this to the 1.0 milestone on Jun 18, 2026
  2. added
    lifecycle/confirmedBug is verified or proposal seems reasonable
    and removed on Jun 18, 2026
  3. jprendes commented on Aug 10, 2026

    @jprendes
    Contributor

    AFAICT, SandboxRuntimeConfig is not a public struct so it's not part of the public API.

  4. syntactically commented on Aug 11, 2026

    @syntactically
    Member

    AFAICT, SandboxRuntimeConfig is not a public struct so it's not part of the public API.

    I don't think that was intentional, if that is the case. @ludfjig ?

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

Metadata

Metadata

Assignees

Labels

lifecycle/confirmedBug is verified or proposal seems reasonable

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions