Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

asyncFlow packaging should provide endowments, meta-operations #9304

Open
Tracked by #9281
erights opened this issue Apr 28, 2024 · 1 comment
Open
Tracked by #9281

asyncFlow packaging should provide endowments, meta-operations #9304

erights opened this issue Apr 28, 2024 · 1 comment
Assignees
Labels
asyncFlow related to membrane-based replay and upgrade of async functions bug Something isn't working

Comments

@erights
Copy link
Member

erights commented Apr 28, 2024

See #9097

This does not affect the low level asyncFlow abstraction itself. But such conveniences must appear at the abstraction level immediately above it.

@mhofman , I'll leave this for you to describe, since you're already writing about this.

@erights erights added bug Something isn't working asyncFlow related to membrane-based replay and upgrade of async functions labels Apr 28, 2024
@aj-agoric aj-agoric assigned iomekam and unassigned erights May 13, 2024
@erights
Copy link
Member Author

erights commented May 17, 2024

For example, should add a meta operation for asking about the incarnation number of the next log state, that does not log the query, but would always give the same answer if asked at the same point. This would permit a successor to ask when its predecessor did not, and vice versa. (Suggested by @dtribble I think)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
asyncFlow related to membrane-based replay and upgrade of async functions bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants