Hello all, Where I work, we like to inject module dependencies during compile time. So for example, I can have MyModule for dev and prod builds, but for test I might have MyModuleStub. So let’s say I have a code like this: # ... @the_module Application.compile_env!(:my_app, :the_module) #... cas…

I’m not sure how to solve this with the current capabilities, but I think it’s funny that the main complaint about the type system is that it is too smart :grinning:

[image] Elixir v1.18.0-rc.0 released Elixir News The trick we are using in Elixir test suite under similar situations (when we need to force the code to crash to test error handlers and similar) is to hide the value under Process.get(:unused_key, value). For example: Proc…

Thank you. It is what we ended up doing.

Another option, if Process.get(...) is too magical, is to pretend that you can return something else: if :rand.uniform() >= 0 do # always true {:ok, ...} else :error end Once we add behaviours to the type system, this warning will disappear, but for now we need to rely on one of the followin…

I’m also encountering a similar issue in my ExUnit tests. For example, I have tests like this: defmodule MyApp.MyTest do use ExUnit.Case, async: true setup do foo = produce_test_data(1, 2, 3) bar = produce_test_data(4, 5, 6) refute match?(^foo, bar) end test "..." do # u…

Elixir V 1.18 behaviours and different builds warnings

Questions & Help Questions

LostKobrakai January 9, 2025, 10:43am 3