Skip to content

svd2rust-regress usability woes #355

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

Closed
therealprof opened this issue Jul 30, 2019 · 1 comment · Fixed by #728
Closed

svd2rust-regress usability woes #355

therealprof opened this issue Jul 30, 2019 · 1 comment · Fixed by #728

Comments

@therealprof
Copy link
Contributor

therealprof commented Jul 30, 2019

The interface of svd2rust-regress is a bit iffy. On one hand internally every manufacturer and chip name is converted to a "nice" lower-case name with no special characters and this is used everywhere, also for the output of the --list option. On the other hand all options like --manufacturer and --chip expect to receive the unchanged original name.

Also wildcards are not supported which would be really nice to have.

Next problem is that bad tests are only listed or can be executed when the --bad-tests option is supplied however I'd expect to see bad tests in the listing as well (maybe with some additional marker) to know that they exists and also to execute them without having to explicitly specify that it's in the "bad tests" category when I specifically ask for a certain chip.

@burrbull
Copy link
Member

related to #728

@Emilgardis Emilgardis mentioned this issue Dec 6, 2023
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants