-
Notifications
You must be signed in to change notification settings - Fork 51
Does T-lang have opinion on floating-point guarantees? #210
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
Comments
(this came up in T-opsem backlog bonanza today and after a couple rounds of interrogation, I said I would bring it up with T-lang today.) |
We talked about this somewhat during today's @rust-lang/lang meeting. From that discussion, it's safe to say that the team does have various opinions on floating-point guarantees. :) We're going to have further discussion around this in the context of language design principles, and then after that, see if someone wants to champion some design for floating-point guarantees in particular. |
@rustbot labels -I-lang-nominated Conclusion from our meeting today: Yes, lang team cares, we would be happy to make decisions, but we would need a design meeting to get a real understanding. |
T-opsem wants to know if T-lang has a current opinion, or believes it may want to have a future opinion, about: rust-lang/unsafe-code-guidelines#123
The text was updated successfully, but these errors were encountered: