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

Chaging data types to avoid dangerous conversions #348

Merged
merged 2 commits into from
Oct 2, 2024
Merged

Conversation

pablodeymo
Copy link
Contributor

Fixes # .

What Changed?

Reviewer Checklist

  • Code is well-documented
  • Code adheres to Go naming conventions
  • Code deprecates any old functionality before removing it

Copy link
Contributor

@juanbono juanbono left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@samlaf samlaf force-pushed the datatype_conversion branch from 46dc6a0 to 75089de Compare September 27, 2024 20:53
@samlaf samlaf enabled auto-merge September 27, 2024 20:53
@pablodeymo pablodeymo requested a review from afkbyte October 2, 2024 15:41
@afkbyte afkbyte force-pushed the datatype_conversion branch from 75089de to 62be544 Compare October 2, 2024 21:54
@samlaf samlaf added this pull request to the merge queue Oct 2, 2024
Merged via the queue into dev with commit ab474fb Oct 2, 2024
4 checks passed
@samlaf samlaf deleted the datatype_conversion branch October 2, 2024 22:00
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