Skip to content

Tracking issue for RFC 36: Async testbench functions #1213

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

Open
zyp opened this issue Mar 18, 2024 · 3 comments
Open

Tracking issue for RFC 36: Async testbench functions #1213

zyp opened this issue Mar 18, 2024 · 3 comments
Labels
Milestone

Comments

@zyp
Copy link
Contributor

zyp commented Mar 18, 2024

@whitequark
Copy link
Member

This still needs to be documented, so I'll keep it open for now.

@whitequark whitequark modified the milestones: 0.5, 0.6 Jun 10, 2024
@cr1901
Copy link
Contributor

cr1901 commented Jun 15, 2024

This still needs to be documented, so I'll keep it open for now.

Will generator functions be deprecated in 0.6 instead of 0.5? async testbenches made the 0.5 cutoff, and the RFC mentions deprecation of generator functions at the very end. But I don't see anything about deprecation in the CHANGELOG/porting guide from 0.4 to 0.5.

(Basically, "I'd like to quickly migrate to 0.5 and cut a release of some packages without upgrading generator testbenches to async for now.")

@whitequark
Copy link
Member

Generator functions are deprecated in 0.5 and this is mentioned in the porting guide:

Convert simulator processes and testbenches to use the new async API.

However the deprecation fell through the cracks. (@wanda-phi do you think you can do another changelog backport PR?)

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

No branches or pull requests

3 participants