Fix type definition

[paulo-ferraz-oliveira]

+ @type parsec_success :: {:ok, tokens, String.t(), context(), integer(), integer()}
- @type parsec_success :: {:ok, tokens, String.t(), context(), {integer(), integer()}, integer()}

as consumed by e.g. makeup_elixir or makeup_erlang.

I take this time to also introduce dialyxir to CI, which surfaces another issue (opaqueness-related) already mentioned next to stream_data.

Actions missing from this:

• waiting for a stream_data update and subsequent import here
• (potentially) updating nimble_parsec (as per acceptance of this pull request) [optional]

---

Edit: while reading the CONTRIBUTING guide I didn't quite understand how to handle the RELEASE.md part (is this required?). Regarding the CHANGELOG.md, do you prefer I do it? Or do you, prior to release?

[josevalim]

A PR to fix the specs is welcome but we don't plan to introduce dialyzer at the moment, thank you :)

[paulo-ferraz-oliveira]

Sure. I can remove that bit. Thanks.

Edit: regarding the opaqueness-related issue it also only makes sense with dialyzer in place, so that's one less thing to pursue.

[paulo-ferraz-oliveira]

@josevalim, shall I wait for a nimble_parsec release to update this? Or are you good without it? Thanks.

[josevalim]

💚 💙 💜 💛 ❤️

[paulo-ferraz-oliveira]

The goal of this update is to fix a Dialyzer -related issue with makeup_erlang and makeup_elixir (for which now I'm thinking you don't want dialyxir introduced 😄). Do you think it would make sense to tag-release it, to prevent consumers from finding a dialyxir issue.