Fix warnings emitted by elixir 1.18/OTP27#37
Merged
Conversation
Shakadak
reviewed
Nov 5, 2025
Member
Shakadak
left a comment
Shakadak
left a comment
There was a problem hiding this comment.
How about we just go and mix format --migrate using elixir 1.19 ? because these kind of warnings will come back soon
Krapaince
force-pushed
the
fix-elixir-1-18
branch
from
df75ecf to
fe2474f
Compare
Fixes warnings emitted by the Elixir's compiler v1.19. close #36
Krapaince
force-pushed
the
fix-elixir-1-18
branch
from
1d6df5f to
f05db5a
Compare
Shakadak
reviewed
Nov 13, 2025
Member
|
I'm ok with merging. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.