Skip to content

feat(sdk): gate experimental APIs behind feature#1395

Open
chris-olszewski wants to merge 1 commit into
mainfrom
olszewski/feat_experimental_feature2
Open

feat(sdk): gate experimental APIs behind feature#1395
chris-olszewski wants to merge 1 commit into
mainfrom
olszewski/feat_experimental_feature2

Conversation

@chris-olszewski

Copy link
Copy Markdown
Member

What was changed

  • Gate any API and required code marked as "experimental" behind a new experimental feature gate.
  • Build docs with new feature enabled so APIs are discoverable

Why?

Make it explicit at a language level what APIs are experimental compared to just a comment.

Checklist

  1. Closes N/A

  2. How was this tested:
    Existing test suite, ensured we still check that crates compile without feature enabled in CI

  3. Any docs updates needed?
    N/A


/// Optionally enable Eager Workflow Start, a latency optimization using local workers
/// NOTE: Experimental
#[cfg(feature = "experimental")]

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this really still experimental?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so

@chris-olszewski
chris-olszewski marked this pull request as ready for review July 11, 2026 00:49
@chris-olszewski
chris-olszewski requested a review from a team as a code owner July 11, 2026 00:49
@Sushisource

Copy link
Copy Markdown
Member

Still kinda on the fence about if I want to do it this way with actual gates. Feels like it'll make it harder to get feedback on new stuff. Perhaps just experimental in the docstring is sufficient?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants