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

RFC review: Add f16 and f128 float types -- RFC#3453 #218

Closed
pnkfelix opened this issue Sep 12, 2023 · 3 comments
Closed

RFC review: Add f16 and f128 float types -- RFC#3453 #218

pnkfelix opened this issue Sep 12, 2023 · 3 comments
Labels
meeting-proposal Proposal for a lang team design meeting T-lang

Comments

@pnkfelix
Copy link
Member

rust-lang/rfcs#3453

@pnkfelix pnkfelix added meeting-proposal Proposal for a lang team design meeting T-lang labels Sep 12, 2023
@pnkfelix
Copy link
Member Author

scheduled for 2023-09-20

@scottmcm
Copy link
Member

I might not make the meeting for this, but my thoughts are currently like rust-lang/rfcs#3453 (comment) -- that I think from a lang perspective this seems fine, but that actually getting "full" support for things might not happen for a very long time.

So my note for a discussion might be whether we'd be ok with this even if, for a while, say only literals and conversions and ABI support existed for them, perhaps not even things like *.

@aaronfranke
Copy link

@scottmcm I think full support is both ideal and important, but this should not block just getting the type in, if that can be done faster. Having only literals and conversions is better than nothing for now. Basic math operations like addition and multiplication are very important too, only second to literals and conversions, so we must have them eventually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meeting-proposal Proposal for a lang team design meeting T-lang
Projects
Development

No branches or pull requests

4 participants