eksperimental
Is there a way to conditionally import a function, but make the import available outside the if or case?
this obviously works:
def foo() do
import Enum, only: [map: 2]
map(1..5, &IO.inspect(&1))
end
this works as well:
if is_integer(term) do
import Enum, only: [map: 2]
map(1..term, &IO.inspect(&1))
end
this does not work due to lexical scope.
if true do
import Enum, only: [map: 2]
end
map(1..integer, &IO.inspect(&1))
So far so good.
My question is, how can we import conditionally at runtime, and make the import available outside the condition clause.
The only solution that I thought it could make it work was this, it does not and it baffles me.:
true && (import Enum, only: [map: 2])
map(1..integer, &IO.inspect(&1))
Note: for my use case I can solve this by running the condition at compile time, but I am just trying to understand how to do it at runtime.
Thank you
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated!
To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead.
Sta...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
New
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
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
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance










First 6 of 6 Posts
ityonemo
Imports are compile-time.
dimitarvp
Elixir being FP I don’t see any other way except closures or just passing a function like so
Or you can do it with a keyword list parameter with
:doand:elselike theifmacro does.LostKobrakai
That’s what I’d do, which seems a lot cleaner than conditionally importing things.
eksperimental
This is pretty much what i am doing.
It is for a BackPort module, where I give support for older Elixir versions importing functions/macros based on
macro_exported?(Kernel, :macro_name, :arity)It still baffles me why using
&&will not work.I have not read
&&creating a lexical scope within itself.al2o3cr
The behavior makes sense if you look at the implementation:
https://github.com/elixir-lang/elixir/blob/74bfab8ee271e53d24cb0012b5db1e2a931e0470/lib/elixir/lib/kernel.ex#L3791-L3803
The right-hand expression in
&&winds up inside acasestatement, so theimportdoes not leak out.eksperimental
@al2o3cr you are so right! I wrongly assumed that it was &&/2 was inlined by the compiler. I guess it all comes down to this, anyway had it been, it would have been the same:
because this seems to work the same way.
So I guess the only option here is evaluating the condition at compile time.
Thank you all guys for your contributions.