Qqwy
TypeCheck Core Team
I am working on the MapDiff library, so it works better when structs are passed to it.
I wrote the following two doctests:
iex> defmodule Foo do
...> defstruct a: 1, b: 2, c: 3
...> end
...> MapDiff.diff(%Foo{}, %Foo{a: 3})
%{changed: :map_change, struct_name: Foo,
value: %{a: %{added: 3, changed: :primitive_change, removed: 1},
b: %{changed: :equal, value: 2}, c: %{changed: :equal, value: 3}}}
and:
iex> defmodule Bar do
...> defstruct a: 1, b: 2, c: 3
...> end
...> defmodule Baz do
...> defstruct a: "foo", b: "bar", z: "baz"
...> end
...> MapDiff.diff(%Bar{}, %Baz{})
%{added: %Baz{a: "foo", b: "bar", z: "baz"}, changed: :primitive_change,
removed: %Bar{a: 1, b: 2, c: 3}}
However, this will not compile. When running mix test, the following error is thrown:
Compiling 1 file (.ex)
** (CompileError) (for doctest at) lib/map_diff.ex:105: MapDiffTest.Foo.__struct__/1 is undefined, cannot expand struct MapDiffTest.Foo
(stdlib) lists.erl:1354: :lists.mapfoldl/3
test/map_diff_test.exs:3: anonymous fn/3 in :elixir_compiler_1.__MODULE__/1
(elixir) lib/enum.ex:1755: Enum."-reduce/3-lists^foldl/2-0-"/3
test/map_diff_test.exs:3: (module)
I think that this is the case because Elixir tries to evaluate the outcome value decoupled from the example, which means that Foo, Bar and Baz (and their respective __struct__/1 implementations) are not in scope.
Now, how can these doctests be rewritten so:
- they compile.
- it is clear to people that
Foo,BarandBazare normal structs they could define themselves?
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
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
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 2 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Qqwy
Yes! This solution works wonderfully
.
I ended up simply defining the structs in the
tests/map_diff_test.exsfile, inside theMapDiffTestmodule, beforedoctest MapDiffis being called, because it seemed the most clear (as long as the code does not become much longer.)Thank you very much
!
vic
I guess the best would be to define those example structs somewhere like in
test/supportthen just add a comment about their structure on your docs (indent the code four spaces so that it gets properly highlighted as elixir code) and then just import them for doctest: