Skip to content

Should aux methods be unique per qualifier + dispatch value? #100

@camsaul

Description

@camsaul

It gets super confusing when you have multiple aux methods with the same dispatch value, and it can lead to weird gotchas if you rename a namespace or remove them. It's also indeterminate which order they're applied in...

I think there are some valid use cases for things like multiple :around :default methods for logging and other things like that. How can we still support that case?

Maybe we should make the unique key something you can optionally supply yourself, and by default it's nil. So if you want to do something weird you can supply a unique key to prevent it from getting stomped on. Altho I'm not sure that would really solve the renaming namespaces issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions