Open
Description
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.
- Do not add builtins by default #559
- The deprecation of
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.
- The deprecation of
- remove 'array_pkg' #600
- Deprecation was announced 2y ago.
- sim_if/ghdl: remove 'ghdl.flags' #932
- Deprecation was announced 2y ago.
- sim_if: continue after compilation failure if '--keep-compiling' is True #742
- This is to get rid of the custom code in Compliance-Tests (https://github.com/VHDL/Compliance-Tests/blob/master/run.py#L30-L64). That was written before option
--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.
- This is to get rid of the custom code in Compliance-Tests (https://github.com/VHDL/Compliance-Tests/blob/master/run.py#L30-L64). That was written before option
- Remove deprecated 'check', 'log' and 'run' packages. #933
- VHDL 'package name' and 'file name' inconsistencies need to be fixed #760
- Add compliance tests and updated VCs accordingly #520