To simplify some tasks at work, I wrote and published this package yesterday. It’s a simple macro that enables Access behaviour on structs. https://github.com/codedge-llc/accessible So, while I know this goes directly against core design decisions, it makes it extremely simple to perform deeply ne…

I think core’s design decision in this regard is twofold: The compile-time guarantees of struct.field access should be strongly encouraged over the runtime struct[:field] form The creator of the struct might have a different vision for what Access might mean for their data-structure This is why i…

[image] christhekeele: The creator of the struct might have a different vision for what Access might mean for their data-structure I ended up here from trying to ask a new question: Where can one find details on the reasoning behind why Structs in Elixir do not implement the Access behaviour? …

[image] mariusbutuc: If so, since this link is out of date * , where can one find an example of implementing the Access behaviour for Struct s? I believe the approach documented here is now the way to do this.

You can use put_in and get_in on structs like shown by Dogbert in Elixir: best practice to extract data from nested structs on Stackoverflow.

Looks like it is for protocols, not behaviours. I think I will use struct_access to avoid copy/pasting: @behaviour Access defdelegate get(v, key, default), to: Map defdelegate fetch(v, key), to: Map defdelegate get_and_update(v, key, func), to: Map defdelegate pop(v, key), to: Map Note that the po…

You can try macros maybe . import Maybe event = %Event{user: %User{name: "John"}} maybe(event.user.name) # => "John" It’s a slightly modified version of maybe from phoenix_base by Daniel Berkompas

Starting from Elixir 1.17, you can traverse structs using the Kernel.get_in/1 macro # In case any of the keys returns nil, then nil will be returned and get_in/1 won't traverse any further. get_in(struct.foo.bar)