# Idea: In the next edition, stop accepting \`0.\` as a valid float literal

**URL:** https://internals.rust-lang.org/t/idea-in-the-next-edition-stop-accepting-0-as-a-valid-float-literal/10790
**Category:** Uncategorized
**Created:** [August 16, 2019, 6:13pm UTC](https://internals.rust-lang.org/t/idea-in-the-next-edition-stop-accepting-0-as-a-valid-float-literal/10790 "2019-08-16T18:13:56Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![RustyYato](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/rustyyato/32/13627_2.png) [@RustyYato](https://internals.rust-lang.org/u/RustyYato)
#### Post date: [August 17, 2019, 3:14am UTC](https://internals.rust-lang.org/t/idea-in-the-next-edition-stop-accepting-0-as-a-valid-float-literal/10790/7 "2019-08-17T03:14:56Z")

</div>

> [@jethrogb](#):
>
> Except in the most annoying case of `tuple_tuple_struct.0.0` which still won't be legal.

I think we could make that legal, by making it mean the same thing as `(tuple_tuple_struct.0).0` but that is a different discussion.

* * *

link to other thread that I just made for this:

> [@Should we make \`nested\_tuple.0.0\` legal syntax?](https://internals.rust-lang.org/t/should-we-make-nested-tuple-0-0-legal-syntax/10804):
>
> Currently nested\_tuple.0.0 is not legal and gives the following error error: unexpected token: `0.0` --\> src/lib.rs:2:19 | 2 | let x = nested\_tuple.0.0; | ------^^^ | | | | | unexpected token | help: try parenthesizing the first index: `(tuple.0).0` error: aborting due to previous error error: Could not compile `playground`. To learn more, run the command again with --verbose. Could we change this behavior to parse it as…

---

_[View the full topic](https://internals.rust-lang.org/t/idea-in-the-next-edition-stop-accepting-0-as-a-valid-float-literal/10790)._