Skip to content

Fix t:Range.t/2 #10833

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

Merged
merged 1 commit into from
Mar 29, 2021
Merged

Conversation

eksperimental
Copy link
Contributor

We need to be explicit and define the step field, otherwise IEx and ExDoc will spec it as "term()"

(1)> t Range.t/2
@type t(first, last) :: %Range{first: first, last: last, step: term()

We need to be explicit and define the step field, otherwise IEx and ExDoc will spec it as "term()"

    (1)> t Range.t/2
    @type t(first, last) :: %Range{first: first, last: last, step: term()
@josevalim josevalim merged commit 95a6792 into elixir-lang:master Mar 29, 2021
@josevalim
Copy link
Member

💚 💙 💜 💛 ❤️

josevalim pushed a commit that referenced this pull request Mar 29, 2021
We need to be explicit and define the step field, otherwise IEx and ExDoc will spec it as "term()"

    (1)> t Range.t/2
    @type t(first, last) :: %Range{first: first, last: last, step: term()
@eksperimental eksperimental deleted the fix_range_t_2 branch March 29, 2021 20:38
eksperimental added a commit to eksperimental-forks/elixir that referenced this pull request Mar 29, 2021
It improves the changes introduced in 95a6792 (elixir-lang#10833)
As a range defined with only first and last fields should be a consecutive sequence.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants