To be honest, besides the documentation addition, I'd also prefer to add a warning when using a literal that is out of bounds. This behavior seems too unpredictable to me, as is. (Or, should I say, rather surprising.)

It looks like it happens here. Can you give a hint about how to implement such a warning? Or alternatively, I can make it produce an error guiding the user to use a float instead.

We don't yet have any real infrastructure for adding warnings to the parser (I ran into this as well in #5229). We do have error infrastructure, so we could also just start by erroring on out-of-bounds literals. If we do want warnings, then there are many ways we could do so.

One way to add parser warnings may be to add a Warning variant to the SyntaxKind enum and extend the options for SyntaxNode::Repr to include warnings and an interface for creating them. Warning nodes could then transparently wrap an underlying SyntaxNode plus the warning and any hints, and we would expose a new set of functions from SyntaxNode to access them.

However, I would recommend that we discuss if this is the right design before starting to implement it. Best would be to join the contributors channel on Discord, but we could also continue here (maybe in a new issue).

And if you want any help talking through the parser infrastructure, let me know!

Thanks!

Since implementing a warning is a little more complex, let's not block this on it.