Skip to content

Conversation

@workingjubilee
Copy link
Member

Now that we are thoroughly embedded in libcore, we don't need these on by default.
Indeed, their presence may provide confusing results during integration attempts.

Now that we are thoroughly embedded in libcore, we don't need these on by default.
Indeed, their presence may provide confusing results during integration attempts.
type Scalar = $scalar;
type IntScalar = $int_scalar;

#[cfg(feature = "std")]
Copy link
Member

Choose a reason for hiding this comment

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

Do these not require std?

Copy link
Member Author

Choose a reason for hiding this comment

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

So there is a nuance here in that we don't actually have a target that fully lacks libm support (or equivalent) at the moment, and tests bring in std, so we can't reaaally truly sincerely test for that. For making sure the relevant things work properly (or fail properly), there are some UI tests in the compiler's test suite.

@workingjubilee workingjubilee merged commit a5789d1 into master Mar 1, 2022
@workingjubilee workingjubilee deleted the no-default-features branch March 1, 2022 03:57
workingjubilee added a commit that referenced this pull request Jul 19, 2022
Now that we are thoroughly embedded in libcore, we don't need these on by default.
Indeed, their presence may provide confusing results during integration attempts.
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