should one generally put `optional(any) => any` into maps?
Open
deviations from erlang/elixir
- Dominant language
- Elixir
- Stars
- 110
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I think the answer this should be explicit, because something like a struct should not generally have optional(any) => any.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating the map and struct handling in the Elixir library, then review the existing treatment of optional(any) => any and determine what explicit behavior and tests would be needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100