Skip to content

Don't use empty asserts #1019

@timtreis

Description

@timtreis

I remember seeing quite a few GitHub issues that are opened because users run into assert statements that just fail but don't educate the user why they were caused. I think we should have an internal policity to not have that and instead raise proper errors. That'd also make triaging issues for us easier.

Will continue to link related issues below:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions