Fl4m3Ph03n1x

Fl4m3Ph03n1x

Background

I am playing around with defguard in macro I am defining. The macro has an opaque type and I think dialyzer is having issues with this:

macro:

defmodule NewType do

  defmacro deftype(name, type) do
    quote do
      defmodule unquote(name) do
        @opaque t :: {unquote(name), unquote(type)}

        @spec new(value :: unquote(type)) :: t
        def new(value) when is_binary(value), do: {unquote(name), value}

        @spec extract(new_type :: t) :: unquote(type)
        def extract({unquote(name), value}), do: value
      end
    end
  end

  defguard is_type?(value, mod)
           when is_tuple(value) and
                  elem(value, 0) == mod and is_binary(elem(value, 1))
end

In theory, an invocation of deftype Name, String.t() would generate:

defmodule Name do
   @opaque t :: {Name, String.t}

  @spec new(value :: String.t()) :: t
  def new(value) when is_binary(value), do: {Name, value}

  @spec extract(new_type :: t) :: String.t()
  def extract({Name, value}), do: value
end

And in fact, this code works as intended:

type.ex (module where I define several types)

defmodule Type do
  import NewType
  
  deftype Name, String.t()
end

test.ex

defmodule Test do
  alias Type.Name

  @spec print(Name.t()) :: binary
  def print(name), do: Name.extract(name)
end

Problem

The problem arises when I try to use the guard:

test.ex

defmodule Test do
  import NewType
  alias Type.Name

  @spec print(Name.t()) :: binary
  def print(name) when is_type?(name, Name), do: Name.extract(name)
end

Everything runs as expected, but dialyzer does not see it the same way:

lib/test.ex:6:no_return
Function print/1 has no local return.
________________________________________________________________________________
lib/test.ex:6:call_without_opaque
Function call without opaqueness type mismatch.

Call does not have expected opaque term of type Type.Name.t() in the 1st position.

Type.Name.extract(_name :: tuple())

________________________________________________________________________________
done (warnings were emitted)
Halting VM with exit status 2

Even though Name.extract does receive a Name.t as a parameter, dialyzer states otherwise.
At this point, I think this might be because I am “exposing” the internal data structure in the guard with is_tuple, but at the same time, I don’t see how else I can have defguard and still use opaque types.

Question

Am I missing something?

Showing Posts 1 to 1

NobbZ

NobbZ

Dialyzer ignores the spec of Test.print/1, when it has other ways to infer the type of the argument. Due to the use of the is_type?/1 guard, dialyzer infers that the type has to be tuple(). tuple() is not Name.t().

If you deal with opaque types, you can not manually create them, you can not destructure them, you can not use them in guards. You have to pass them around as they are. Only functions in Name are allowed to access its internals.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
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
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
New
RemyXRenard
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
velrest
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
samoloth
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
FlyingNoodle
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
psy-q
I’m trying to set up Emacs with elixir-ls via lsp-mode and credo via Flycheck. This should mostly be preconfigured as Flycheck picks up c...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
marciok
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
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
Damirados
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

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews