Fix Elixir 1.20 compilation warnings - #63
Open
gilbertwong96 wants to merge 1 commit into
Open
Conversation
gilbertwong96
force-pushed
the
fix/elixir-1.20-warnings
branch
from
May 30, 2026 11:08
c2adc91 to
cf0cc9e
Compare
Author
|
Hi, @djm, could you please merge this PR and bump a new version for latest Elixir version ? |
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
1 participant
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.
Resolve compilation warnings introduced in Elixir 1.20.
Map.get(cell, :width_calc, nil)which always returns nil on a%Cell{}struct (the struct doesn't have a:width_calckey). Replaced with directTable.get_column_meta/3call.