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.

Sign up for GitHub

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

Jump to bottom

Revisit how B*P*SSes are serialized. #126

Closed
michbarsinai opened this issue Dec 6, 2020 · 1 comment
Closed

Revisit how B*P*SSes are serialized. #126

michbarsinai opened this issue Dec 6, 2020 · 1 comment
Milestone
Pre-1.0 cleanup

Comments

@michbarsinai
Copy link
Member

Revisit how BPSSes are serialized. Current double serialization might be non-efficient, as the b-threads are serialized in their own streams, which are later added as arrays to the bPss stream.

Also, need to use the same top-level scope as the b-program (see other bug for that).
@michbarsinai michbarsinai added this to the Pre-1.0 cleanup milestone Dec 6, 2020
michbarsinai added a commit that referenced this issue Jan 27, 2021
@michbarsinai
B-threads forget their entry point function when they have a continua…
2e84844 
…tion (part of #126)
@michbarsinai
Copy link
Member Author

Implemented at e9db766.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Pre-1.0 cleanup
Development

No branches or pull requests
1 participant
@michbarsinai