anders
I’m playing around with something like this:
defmodule Todo.User do
defstruct name: nil
end
defmodule Todo.Todo do
defstruct text: nil
def complete(%Todo.Todo{} = todo, %Todo.User{} = completer), do: nil
end
Now, writing %Todo.Todo{} and %Todo.User{} is tedious. Especially if you have a lot of references to the types from a lot of functions. I would prefer %Todo{} and %User{}.
What is the best way of doing this? Is there any good reason not to look for a shorthand here?
I tried this:
defmodule Todo.Todo do
alias Todo.User
alias Todo.Todo
defstruct text: nil
def complete(%Todo{} = todo, %User{} = completer), do: nil
end
and it works, but now the order of the alias:es is important and I have to alias everything with the Todo prefix. Doesn’t feel right.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #elixirconf-us
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
gregvaughn
The module aliases itself? Interesting. I’ve never seen that before. What’s more common is to use
__MODULE__as a compile time reference to the current module.anders
I’ve seen that in GenServers, but how would that translate to this case?
That just looks wierd to me. But I’m new to Elixir, perhaps my eyes haven’t adjusted yet
josevalim
If the naming schema is confusing, I can’t think of a better option besides changing the name. Why not call it
Todo.Listfor the whole list andTodo.ListItemor similar for every element?anders
So in general, avoid using the same name fragments for different parts of the module name?
josevalim
If you want to alias them, then surely. Otherwise you will run into the conflicts you described.