cashews
In this case, considering we don’t have any overlapping function names, is it worth it to use only as a means of asserting that we’re only importing the from public function from the Ecto.Query module or will the compiler tree-shake all unused functions from Ecto.Query regardless?
import Ecto.Query, only: [from: 2]
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
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.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
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 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sodapopcan
The short answer is yes.
To add some pedantry, I wouldn’t call it “treeshaking” per se.
importis more “opening up the module” to use for function resolution, not so much “importing” it as you would think about it in JS. All imported functions are being expanding to their fully qualified names during compilation.While
:onlyisn’t strictly necessary, it is nice for when someone comes blind to a function in your module and it may not be obvious where a particular function is coming from ifimportis used multiple times. With your example ofEcto.Query, though, I never both specifyingfrombecause it’s generally super obvious by the context of the file whatfromis. It’s context-dependent and, of course, a matter of taste!But ya, unused functions are not compiled.
benwilson512
Just to be clear though, the functions will exist inside the
Ecto.Querymodule regardless of whether they are used anywhere or not.importis only lexical, and calls to imported functions are translated into remote calls a laEcto.Query.from.sodapopcan
Ya sorry, very poor wording. And reading over my response I see more poor grammar
