Skip to content
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.

Sign up for GitHub

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

Jump to bottom

should one generally put optional(any) => any into maps? #4

Open
ityonemo opened this issue Sep 22, 2020 · 2 comments
Open

should one generally put optional(any) => any into maps? #4

ityonemo opened this issue Sep 22, 2020 · 2 comments
Labels
deviations from erlang/elixir

Comments

@ityonemo
Copy link
Owner

ityonemo commented Sep 22, 2020 •
edited
Loading

I think the answer this should be explicit, because something like a struct should not generally have optional(any) => any.
@ityonemo
Copy link
Owner Author

ityonemo commented Oct 4, 2020

requires investigation into what common practices happen to be. Lean towards no.

@ityonemo
Copy link
Owner Author

ityonemo commented Oct 4, 2020

consider special-casing a warning because I suspect incorrect typespecs are common.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
deviations from erlang/elixir
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ityonemo