Skip to content

SystemVerilog.definitionParameters does not enforce uniqueness with other names #611

@mkorbel1

Description

@mkorbel1

Describe the bug

It is possible to name a SystemVerilog parameter using SystemVerilog.definitionParameters with a name that conflicts with other names in that module definition (ports, reserved instance/signal names, etc.). This should not be allowed and uniqueness should be enforced.

To Reproduce

No response

Expected behavior

No response

Actual behavior

No response

Additional: Dart SDK info

No response

Additional: pubspec.yaml

Additional: Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions