[moetemp]

What changed?

This PR adds @nexus.close, which marks the method that ends a resource, so async with closes it.

/// @nexus.operation "close-stream"
/// @nexus.close
close: func();

• Python's resource class gets __aenter__ and __aexit__. At the end of the block, _support.exit_close(self, exc) decides if it closes. The close method's parameters must be optional, since the block's end passes none.
• An operation that returns such a resource returns a ResourceCall, which nexgen writes in _resource_call.py. So await client.create_stream(...) and async with client.create_stream(...) both work.

TypeScript and .NET get [Symbol.asyncDispose] and IAsyncDisposable in a follow-up PR.

Why?

The proposal creates a Stream in async with, and the end of the block closes it. A close carries no value. The support package decides the policy, since Workflow code can keep a Stream open for a retry run.

How did you test it?

Link to a test plan if any -

• Unit Tests
• Staging
• End to End Tests

Python tests close a Stream after a clean, a failed and a canceled block. A Workflow block leaves the close to the run.

[moetemp]

Moved to temporalio#369, on main.