Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to parse warning #454

Open
pedrodias opened this issue Mar 17, 2022 · 0 comments
Open

Failed to parse warning #454

pedrodias opened this issue Mar 17, 2022 · 0 comments

Comments

@pedrodias
Copy link

Precheck

  • Take a look at the open issues and be sure that your issue is not already covered. - Done
  • Be sure your versions of Dialyxir and Erlex are up to date. - Done

Environment

  • Elixir & Erlang/OTP versions (elixir --version): 1.12.3

  • Which version of Dialyxir are you using? (cat mix.lock | grep dialyxir): 1.1.0

Current behavior

  • The function might return nil and dialyzer is not able to understand it the signature is @spec format(Test.t()) :: %{a: String.t(), b: String.t(), c: String.t()} | nil
  • Failed to parse warning:
    [{:_, 1}, {:atom_part, 1, 'e'}, {:atom_part, 1, 'v'}, {:atom_part, 1, 'e'}, {:atom_part, 1, 'n'}, {:atom_part, 1, 't'}, {:atom_part, 1, '@'}, {:int, 1, 1}, {:=, 1}, {:"#", 1}, {:"{", 1}, {:atom_full, 1, ''c''}, {:":=", 1}, {:<, 1}, {:<, 1}, {:int, 1, 5420150534173238789090862131555}, {:":", 1}, {:int, 1, 104}, {:>, 1}, {:>, 1}, {:"}", 1}]

Expected behavior

  • To the warning to be parsed
@pedrodias pedrodias changed the title Failed to parse Failed to parse warning Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant