Generalize the warning about combining number literals with decimal places with integer-type suffixes

Open Beginner friendly
#13,384 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Tegrask is already working on this.

Since Nov 15, 2026.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown, powershell
Domain
documentation

Research direction

Read reference/7.7/Microsoft.PowerShell.Core/About/about_Numeric_Literals.md and find the warning about double real literals with a long-type suffix. Update it to explain that the behavior applies to all integer-type suffixes, using the examples in the issue as guidance; done when the warning describes the broader set accurately.

Written by the indexing model from the issue text.

Description

needs-triage
Type of issue

Missing information

Feedback

The warning in question currently reads:

The syntax permits a double real literal to have a long-type suffix

However, it isn't just the [long] type suffix (l or L) that the behavior applies to, it is ALL integer-type suffixes (y, uy, s, us, ...)

E.g., 1.5y and 2.5y both result in [sbyte] value 2.

Page URL

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_Numeric_Literals?view=powershell-7.7

Content source URL

https://github.com/MicrosoftDocs/PowerShell-Docs/blob/main/reference/7.7/Microsoft.PowerShell.Core/About/about_Numeric_Literals.md

Author

@sdwheeler

Platform Id

dac0e2f9-5d6c-27aa-4439-31eec1460c43

Document Id

39e82455-dbc6-c9a1-5476-e7577feace13

Dominant language
PowerShell
Stars
2.6k
Forks
1.7k
Avg merge
1d 4h
Merged PRs (30d)
4

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MicrosoftDocs/PowerShell-Docs

All issues in MicrosoftDocs/PowerShell-Docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.