Skip to content

fix: Use usize size for usize::from_le_bytes buffer #88

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

Merged
merged 1 commit into from
Mar 5, 2021

Conversation

morenol
Copy link
Collaborator

@morenol morenol commented Mar 5, 2021

Fixes #87

@morenol
Copy link
Collaborator Author

morenol commented Mar 5, 2021

@ronniec95 I would appreciate if you confirm me that this fixes #87 for your use case. I am going to check which images we can use to run the build tests with other architectures

@morenol morenol changed the title fix: Use usize time for usize::from_le_bytes buffer fix: Use usize size for usize::from_le_bytes buffer Mar 5, 2021
@morenol morenol requested a review from VolodymyrOrlov March 5, 2021 14:58
@morenol
Copy link
Collaborator Author

morenol commented Mar 5, 2021

Before merging this @VolodymyrOrlov I would like to add a way in the CI to check the building of smartcore for different architectures and OS, what do you think if we move to Github Actions?

@VolodymyrOrlov
Copy link
Collaborator

@morenol I am fine as long as Github Actions supports all build steps.

@morenol morenol merged commit abeff79 into smartcorelib:development Mar 5, 2021
@morenol morenol deleted the lmm/use_usize_size branch March 5, 2021 21: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.

mod.rs deserialize_data uses architecture specific usize which errors on 32bit linux/windows
2 participants