Skip to content

Fix compiler warnings related to Crystal 1.14#232

Closed
mloughran wants to merge 2 commits intoanykeyh:masterfrom
mloughran:fix-1.14
Closed

Fix compiler warnings related to Crystal 1.14#232
mloughran wants to merge 2 commits intoanykeyh:masterfrom
mloughran:fix-1.14

Conversation

@mloughran
Copy link
Copy Markdown
Contributor

Description

This fixes compiler warnings, which I've detailed in the commit commits. This should be a no-op change.

Motivation and Context

Clean buids.

How Has This Been Tested?

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Manual of usage of the new feature.

Checklist:

  • My code follows the code style of this project. bin/ameba ran without alert.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

Fixes deprecation warnings of the form:

```
In spec/sql/select/lock_spec.cr:22:7

 22 | sleep(0.05) # Give hand to the other fiber. Now it should be not locked anymore?
      ^----
Warning: Deprecated ::sleep. Use `::sleep(Time::Span)` instead
```
Fixes:

```
In src/clear/expression/expression.cr:86:17

 86 | def to_json(b = nil)
                  ^
Warning: positional parameter 'b' corresponds to parameter 'x' of the overridden method Clear::Expression::Literal#to_json(x : JSON::Builder), which has a different name and may affect named argument passing
```
@mloughran mloughran changed the title Fix compiler warnings related to crystal 1.14 Fix compiler warnings related to Crystal 1.14 Jan 3, 2025
@mloughran
Copy link
Copy Markdown
Contributor Author

@anykeyh it looks like you've implemented the same changes in #234 – feel free to merge this, or I will close.

@anykeyh
Copy link
Copy Markdown
Owner

anykeyh commented Sep 4, 2025

Yeah, I will close this one, as I added the changes in 0.10

@anykeyh anykeyh closed this Sep 4, 2025
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.

2 participants