-
Notifications
You must be signed in to change notification settings - Fork 263
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
Deprecations: preparation for VUnit-V #763
Labels
Milestone
Comments
This was referenced Apr 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are several packages and features in VUnit that have been deprecated for months. Maybe it's time to decide about removing all of them at once. We are about to release v4.6.0. If we include breaking changes, the next one would be v5.0.0. I thought it might be fun to use roman numbers and have a banner imitating RISC-V:
Anyway, that's the least important. We need to review which features were marked/announced as deprecated already, and which need to be marked in v4.6.0 so we can then remove them in v5. There are milestone v5.0.0 and label 'breaking change' for keeping track of issues related to this deprecation window.
compile_builtins
andvunit.verilog
, along with replacingadd_builtins
withadd_verilog_builtins
andadd_vhdl_builtins
was announced already (see add 'compile_builtins' deprecation warning #757). remove compile_builtins and vunit.verilog #764 is to be merged in a future v5 release.--keep-compiling
was added to VUnit. However, we need it to keep running, not to stop after compilation. Anyway, it is strictly a breaking change, as proven by the failing CI test.The text was updated successfully, but these errors were encountered: