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

Add an explicit step to a range match #195

Closed
wants to merge 2 commits into from
Closed

Add an explicit step to a range match #195

wants to merge 2 commits into from

Conversation

alco
Copy link

@alco alco commented May 24, 2024

Without this, Elixir 1.17 emits a warning for this line.

Without this, Elixir 1.17 emits a warning for this line.
@coveralls
Copy link

coveralls commented May 25, 2024

Pull Request Test Coverage Report for Build c83e3588e67df37d77907aebf33e7a9d83d9a54d-PR-195

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.0%) to 94.656%

Totals Coverage Status
Change from base Build 5f7344ff9642ae88bc6d333ed26cc58f4fdeda87: 1.0%
Covered Lines: 372
Relevant Lines: 393

💛 - Coveralls

@whatyouhide
Copy link
Owner

CI is failing, mind taking a look? We might have to do this conditionally based on the Elixir version, I’m not sure. I'll be without a laptop til Monday so I can't check til then.

@alco
Copy link
Author

alco commented May 28, 2024

@whatyouhide I have rewritten the pattern matching to use the Range struct. If that looks to weird, then never mind. It's not a critical warning to address of compatibility with Elixir v1.11 is a must.

@whatyouhide
Copy link
Owner

Actually, yeah that's a good point. I just dropped support for Elixir 1.11 and fixed this in the latest commit. Thanks @alco 💟

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

Successfully merging this pull request may close these issues.

3 participants