-
Notifications
You must be signed in to change notification settings - Fork 61
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
No std support #110
No std support #110
Conversation
Excellent! I will look closer at it tomorrow (I think), but until then, leave the version as 0.4. I have a script for incrementing it automatically throughout the project when I'm preparing a release, so I will make it find that one as well. |
Oh, and those test results are way off! I didn't think the soft floats would differ that much... |
…ith "std" disabled
I ran some tests, and |
Didn't know |
Maybe I should have checked your last commit... Then I would have known where most some of it came from. 😛 |
Hi! I'm just checking in to see how it's going. If you are just taking a break or on vacation, or similar, I'll leave you to enjoy that. Otherwise let me know if you are getting stuck somewhere or if anything else came in the way. Also, I wanted to check if you have followed the recent development over at https://github.com/japaric/libm. It has gotten a ton of help during the last few weeks, so it's almost feature complete. Would be nice to only have to depend on that one library. |
Sorry I haven't been working on this for a couple weeks -- I was of town for a while, and then just didn't get back to it. There are a few things left in this:
|
Alright, no hurry. 🙂
|
palette/tests/convert/lab_lch.rs
Outdated
@@ -7,8 +7,8 @@ fn lab_lch_green() { | |||
let expect_lab = lch.into_lab(); | |||
let expect_lch = lab.into_lch(); | |||
|
|||
assert_relative_eq!(lab, expect_lab, epsilon = 0.001); | |||
assert_relative_eq!(lch, expect_lch, epsilon = 0.001); | |||
assert_relative_eq!(lab, expect_lab, epsilon = 0.1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you tried tightening these error margins again?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have -- it works fine 😃 thanks to libm
.
I'll push those changes in a moment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! 😄
I expect this CI run to fail, because of rust-lang/libm#4. I could only get it to work by running it with
|
I appreciate that you are already on the case with PRs! Hopefully we can get away with just a few of those, because I would really like to wait for it to be fixed in What's your view on it? You are putting in a lot of work to get this through (which I once again appreciate a lot) and I don't want it to turn into a burden for you, rather than something enjoyable. |
The only necessary PR's to libm are for atan2 and sqrt; the others work fine. Here's an idea:
|
Sounds like a plan! |
By the way, I have a PR up with a quick fix for the hygiene warning and will make a release within the next day or so. Then I'll also merge those changes into |
The fix is in |
I just pushed a merge from I think it's OK to merge, waiting on reverting the float trait once the libm PR's are in and released. |
(As a side note -- the docs link in |
Thanks! I saw that one of the travis jobs timed out, so I restarted it, but I'll merge it when it's all green. If you have your revert ready, you can upload it and open a PR that can stay open until it's time. Otherwise I'll make an issue for it so it's not forgotten.
Oh, you're right. It's supposed to be symlinked to the root README.md, but I must have messed something up... |
bors: r+ |
110: No std support r=Ogeon a=mb64 Adds support for using palette without the standard library, as discussed in issue #108. Fixes #108. One tiny question: because this would be in a future release (not 0.4.0), what version should be in the README example Cargo.toml for `#![no_std]`? I put 0.4, but was unsure about if it should be something different. Co-authored-by: Mark Barbone <mark.l.barbone@gmail.com>
Build succeeded |
Adds support for using palette without the standard library, as discussed in issue #108.
Fixes #108.
One tiny question: because this would be in a future release (not 0.4.0), what version should be in the README example Cargo.toml for
#![no_std]
? I put 0.4, but was unsure about if it should be something different.