Marcel Otto

Are you running on a Mac with a M1? Then you're probably running into this issue: https://github.com/jayjun/rambo/pull/13 The (hopefully temporary) solution mentioned there, worked for me: > It only worked...

I'm getting the same error in a project with some parsers generated with Erlang's leex and yecc: ``` Please file a bug in https://github.com/jeremyjh/dialyxir/issues with this message. Unknown error occurred:...

The errors I've reported are from https://github.com/rdf-elixir/rdf-ex. However, I'm only getting them locally (under Elixir 1.12.2 and OTP 24.0.1), but not on CI with the same versions, which makes me...

My bad. I assumed that `mix dialyzer.clean` would do that. Sorry for the noise. And thanks for the check and the hint (and maintaining this great project in general).

Before you start investigating further, let me try a manual cleanup when I'm back home. I just answered your last comment quickly during a break in my day job.

Ok, `mix dialyzer.clean` successfully deletes the PLT file. So, I guess something else in my local environment must be the cause.

Although unrelated to this issue, I thought I share the final solution to the occurrence of this error in the context of leex and yecc parsers, just if someone else...

> Regarding adding :error tuple, I'm not entirely sure. It might perhaps complicate the expectation of Saxy.parse_string/3 for the error case 🤔. What values would you think adding :error would...

Sure, no problem. I'm already working with the current approach. It was just a suggestion for improvement. But I actually went with `:halt`, since returning an error with `:stop` hampers...

I wanted to use the new capability from Elixir 1.11 to use the `map.field` syntax in guards and stumbled across the false warning from this issue similarly. Other than the...