René's URL Explorer Experiment


Title: Allow binary numbers, byte literals, and BigInteger? · Issue #7557 · PowerShell/PowerShell · GitHub

Open Graph Title: Allow binary numbers, byte literals, and BigInteger? · Issue #7557 · PowerShell/PowerShell

X Title: Allow binary numbers, byte literals, and BigInteger? · Issue #7557 · PowerShell/PowerShell

Description: I will attempt to summarise here the primary points of discussion that have ensued in #7993 as it has spiraled into many threads, and I suspect a bullet-point summary of questions to be answered will be significantly easier on the commit...

Open Graph Description: I will attempt to summarise here the primary points of discussion that have ensued in #7993 as it has spiraled into many threads, and I suspect a bullet-point summary of questions to be answered wi...

X Description: I will attempt to summarise here the primary points of discussion that have ensued in #7993 as it has spiraled into many threads, and I suspect a bullet-point summary of questions to be answered wi...

Opengraph URL: https://github.com/PowerShell/PowerShell/issues/7557

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Allow binary numbers, byte literals, and BigInteger?","articleBody":"I will attempt to summarise here the primary points of discussion that have ensued in #7993 as it has spiraled into many threads, and I suspect a bullet-point summary of questions to be answered will be significantly easier on the committee. \r\n\r\n## Regarding Binary & Hex Parsing\r\n\r\nAs part of the refactor & introduction of binary parsing, methodology of hex parsing has also been altered a bit. Parsing currently _results_ in the same as it currently works, with the caveat that literals with values above `Int64.MaxValue` are also now acceptable.\r\n\r\n### Parse as C# Literals\r\n\r\nWith that in mind, @mklement brought up the point that we may want to simply _change_ how hex and binary parsing work. That is, mimic C#'s behaviour of these literals in source, which would mean parsing _all_ hexadecimal literals as strictly positive (no more `0xFFFFFFFF -eq -1` — instead, `0xFFFFFFFF -eq UInt32.MaxValue`) **and** having such literals smoothly convert up to `UInt` values. \r\n\r\nWith that in mind, the code patterns for hex or binary literals would seek out the lowest available parsed value type (when no type is specified) in the following order: `Int32`, `UInt32`, `Int64`, `UInt64`, `Decimal`, and possibly finally `BigInteger`.\r\n\r\n### Other Options\r\n\r\n#### Hex & BigInteger\r\n\r\nIf we elect to _keep_ current hex behaviour, we need to consider how it would behave in ranges higher than `Decimal`. `BigInteger`'s default parser for hex numerals will simply assume the highest bit of a byte is indicative of the sign. As a result any numeral treated as signed that begins with `0x8` or higher will be considered the negative two's complement representation when we enter ranges that can only be parsed as `BigInteger`. This could be overridden easily, if this behaviour is considered to be undesirable.\r\n\r\n#### Binary Parsing with Sign Bits\r\n\r\nThen we face the issue of what to do about binary parsing. I doubt most folks working with binary directly will be working in ranges above 32-bit numbers, but I could be very wrong on that. They are, however, easier to work with in the `byte`, `short`, and `int` value ranges (8, 16, 32-length literals), and behaviour of a sign bit in this case is _also_ entirely up to the parser here due to the custom implementation of binary parsing for speed concerns.\r\n\r\nShould binary sign bits only be accepted at 32-bit lengths and up for consistency with hex parsing? Or should they be accepted at similar _lengths_ of literal (8 binary bits, 8 hex char literal) to match up visually with hex literals? This would place a sign bit at _all_ of the 8, 16, and 32-char lengths of a binary literal, so `0b11111111 -eq -1` and so forth, which looks similar in behaviour to hex's `0xFFFFFFFF -eq -1`, despite the obvious difference in actual bit length of the literals.\r\n\r\n## Parse Numeric Literals with Underscores\r\n\r\nE.g., `1_000_000`, `0b0101_1010`, `0xF_FFF_F_FFF` and so forth. Should this be allowed? C# already does this with literals in source code. Are there culture-sensitive concerns around this? This is a relatively simple addition.\r\n\r\n## Experimental Feature Possibilities\r\n\r\nIf this is the best option, I am not at all against hiding alternate parse methods behind experimental flags if need be. But for that to be possible, I need a \"standard\" acceptable behaviour to be defined clearly so that I can lay it out for the hex and binary parse methods.\r\n\r\n---\r\n\r\nOriginal post is below. PR #7901 added byte literals (suffix `y` or `uy`), so that portion of this issue is completed.\r\n\r\n---\r\nSee the discussion in #7509.\r\n\r\nEmerging from the interesting dust of modifying the tokenizer are two further points:\r\n\r\n1. The tokenizer should be able to parse binary literals.\r\n2. The tokenizer should support `byte` type literals.\r\n\r\nThe *trouble* here is that both of these suggestions could arguably use a `b` suffix for numeric literals.\r\n\r\nMy opinion is that the `b` *suffix* should be used for `byte` literals, in keeping with the current convention that suffixes alter the numeric *data* type rather than simply base representation.\r\n\r\nSo what about binary? Well, **jcotton** in the PowerShell Slack channel / irc / discord #bridge channel mentioned that just like common hex representations use `0xAAFF057`, we could also follow the common convention of binary being similar: `0b01001011`\r\n\r\nFrom my brief poking about, it *looks* like we may have to alter `System.Globalization.NumberStyles` in order to add `Binary` as a flag value -- *if* we follow the current implementation of hexadecimal numerals. We don't necessarily have to. \r\n\r\n`TryGetNumberValue` in the `tokenizer.cs` file would also have to be modified to accept possibly some kind of `enum` for number formats as well; currently it only accepts a `bool` for `hex` specification. `ScanNumberHelper` would also have to be modified for this.\r\n\r\nThe suffix approach is simpler, especially with the changes already in #7509 which make adding suffixes a good deal easier. However, given that we may want to reserve the `b` suffix for `123b` *byte* literals, we may need to consider adding a case for `0b0010101` syntax.\r\n\r\nWhat do you guys think?\r\n\r\nOther suggested suffixes for byte literals:\r\n\r\n* `ub` ( `sb` or `b` for signed bytes)\r\n* `uy` ( F# style) with `y` for signed bytes\r\n","author":{"url":"https://github.com/vexx32","@type":"Person","name":"vexx32"},"datePublished":"2018-08-17T01:13:35Z","url":"https://github.com/PowerShell/PowerShell/issues/7557"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322
route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:f6a50778-22af-8439-39e6-6edbe8f7b517
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idBB26:19E595:1975B9:2210FE:6AFD4300
html-safe-nonced674c2332bd4de5b11ac4532f0cd74a3897fae56a3f90e61d94ef97f8e2edbbf
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCQjI2OjE5RTU5NToxOTc1Qjk6MjIxMEZFOjZBRkQ0MzAwIiwidmlzaXRvcl9pZCI6IjUwNzcwOTk3MTg3Nzc4NDg1NzYiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ==
visitor-hmac46185f71b6a2849972543246fe1c522f9b7af5819987cd5f6e4086a7e22241c7
hovercard-subject-tagissue:351423441
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/PowerShell/PowerShell/7557/issue_layout
twitter:imagehttps://opengraph.githubassets.com/545bb6747a7a1182d997722c34e6833fe50fd85bab90cbf037babd86c60bf5ef/PowerShell/PowerShell/issues/7557
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/545bb6747a7a1182d997722c34e6833fe50fd85bab90cbf037babd86c60bf5ef/PowerShell/PowerShell/issues/7557
og:image:altI will attempt to summarise here the primary points of discussion that have ensued in #7993 as it has spiraled into many threads, and I suspect a bullet-point summary of questions to be answered wi...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernamevexx32
hostnamegithub.com
expected-hostnamegithub.com
Nonebdbacc25b921224ff0befcb9e629560a1255be51aec9991d6e3f95b5e9151474
turbo-cache-controlno-preview
go-importgithub.com/PowerShell/PowerShell git https://github.com/PowerShell/PowerShell.git
octolytics-dimension-user_id11524380
octolytics-dimension-user_loginPowerShell
octolytics-dimension-repository_id49609581
octolytics-dimension-repository_nwoPowerShell/PowerShell
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id49609581
octolytics-dimension-repository_network_root_nwoPowerShell/PowerShell
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release556dd37bb0aceffb25724e151b5d858b3265b40b
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/PowerShell/PowerShell/issues/7557#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2FPowerShell%2FPowerShell%2Fissues%2F7557
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2FPowerShell%2FPowerShell%2Fissues%2F7557
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=PowerShell%2FPowerShell
Reloadhttps://github.com/PowerShell/PowerShell/issues/7557
Reloadhttps://github.com/PowerShell/PowerShell/issues/7557
Reloadhttps://github.com/PowerShell/PowerShell/issues/7557
PowerShellhttps://github.com/PowerShell
PowerShellhttps://github.com/PowerShell/PowerShell
Codehttps://github.com/PowerShell/PowerShell
Issues1.3k (1.3k)https://github.com/PowerShell/PowerShell/issues
Pull requests364 (364)https://github.com/PowerShell/PowerShell/pulls
Discussionshttps://github.com/PowerShell/PowerShell/discussions
Actionshttps://github.com/PowerShell/PowerShell/actions
Projectshttps://github.com/PowerShell/PowerShell/projects
Security and quality3 (3)https://github.com/PowerShell/PowerShell/security
Insightshttps://github.com/PowerShell/PowerShell/insights
https://github.com/PowerShell/PowerShell
New issuehttps://github.com/login?return_to=https://github.com/PowerShell/PowerShell/issues/7557
New issuehttps://github.com/login?return_to=https://github.com/PowerShell/PowerShell/issues/7557
#7993https://github.com/PowerShell/PowerShell/pull/7993
Allow binary numbers, byte literals, and BigInteger?https://github.com/PowerShell/PowerShell/issues/7557#top
#7993https://github.com/PowerShell/PowerShell/pull/7993
Committee-ReviewedPS-Committee has reviewed this and made a decisionhttps://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22Committee-Reviewed%22
Issue-Enhancementthe issue is more of a feature request than a bughttps://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22Issue-Enhancement%22
Resolution-FixedThe issue is fixed.https://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22Resolution-Fixed%22
WG-Languageparser, language semanticshttps://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22WG-Language%22
https://github.com/vexx32
Rain Sallow (/u/ta11ow) (vexx32)https://github.com/vexx32
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issue-351423441
#7993https://github.com/PowerShell/PowerShell/pull/7993
mklementhttps://github.com/mklement
#7901https://github.com/PowerShell/PowerShell/pull/7901
#7509https://github.com/PowerShell/PowerShell/pull/7509
#7509https://github.com/PowerShell/PowerShell/pull/7509
Nexthttps://github.com/PowerShell/PowerShell/issues/7557?timeline_page=1
https://github.com/rjmholt
Rob Holt (rjmholt)https://github.com/rjmholt
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-413748704
https://github.com/vexx32
Rain Sallow (/u/ta11ow) (vexx32)https://github.com/vexx32
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-413751526
https://github.com/iSazonov
Ilya (iSazonov)https://github.com/iSazonov
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-413753064
Ilya (iSazonov)https://github.com/iSazonov
Issue-Enhancementthe issue is more of a feature request than a bughttps://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22Issue-Enhancement%22
WG-Languageparser, language semanticshttps://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22WG-Language%22
Review - CommitteeThe PR/Issue needs a review from the PowerShell Committeehttps://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22Review%20-%20Committee%22
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#event-1793841061
https://github.com/vexx32
Rain Sallow (/u/ta11ow) (vexx32)https://github.com/vexx32
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-413753889
https://github.com/jcotton42
Josh Cotton (jcotton42)https://github.com/jcotton42
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-413755423
Ilya (@iSazonov)https://github.com/iSazonov
https://github.com/vexx32
Rain Sallow (/u/ta11ow) (vexx32)https://github.com/vexx32
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-413847134
https://github.com/iSazonov
Ilya (iSazonov)https://github.com/iSazonov
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-413866805
https://github.com/vexx32
Rain Sallow (/u/ta11ow) (vexx32)https://github.com/vexx32
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-413873624
https://stackoverflow.com/questions/5378036/literal-suffix-for-byte-in-nethttps://stackoverflow.com/questions/5378036/literal-suffix-for-byte-in-net
https://github.com/iSazonov
Ilya (iSazonov)https://github.com/iSazonov
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-413883654
dotnet/csharplang#1058https://github.com/dotnet/csharplang/issues/1058
https://github.com/vexx32
Rain Sallow (/u/ta11ow) (vexx32)https://github.com/vexx32
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-413886897
https://github.com/iSazonov
Ilya (iSazonov)https://github.com/iSazonov
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-413927136
https://github.com/rjmholt
Rob Holt (rjmholt)https://github.com/rjmholt
on Aug 17, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-413936656
Ilya (@iSazonov)https://github.com/iSazonov
https://github.com/vexx32
Rain Sallow (/u/ta11ow) (vexx32)https://github.com/vexx32
on Oct 7, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-427677696
HumanEquivalentUnithttps://github.com/HumanEquivalentUnit
https://github.com/iSazonov
Ilya (iSazonov)https://github.com/iSazonov
on Oct 12, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-429266495
Steve Lee (@SteveL-MSFT)https://github.com/SteveL-MSFT
https://github.com/mklement0
Michael Klement (mklement0)https://github.com/mklement0
on Oct 22, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-431886299
#7993 (comment)https://github.com/PowerShell/PowerShell/pull/7993#issue-222151965
https://github.com/vexx32
Rain Sallow (/u/ta11ow) (vexx32)https://github.com/vexx32
on Oct 22, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-431889793
Rain Sallow (/u/ta11ow) (vexx32)https://github.com/vexx32
on Nov 15, 2018https://github.com/PowerShell/PowerShell/issues/7557#event-1969732293
https://github.com/vexx32
Rain Sallow (/u/ta11ow) (vexx32)https://github.com/vexx32
on Nov 15, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-439193750
Steve Lee (@SteveL-MSFT)https://github.com/SteveL-MSFT
Michael Klement (@mklement0)https://github.com/mklement0
Ilya (@iSazonov)https://github.com/iSazonov
#7993https://github.com/PowerShell/PowerShell/pull/7993
https://github.com/SteveL-MSFT
Steve Lee (SteveL-MSFT)https://github.com/SteveL-MSFT
on Nov 15, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-439195811
Rain Sallow (/u/ta11ow) (@vexx32)https://github.com/vexx32
https://github.com/SteveL-MSFT
Steve Lee (SteveL-MSFT)https://github.com/SteveL-MSFT
on Nov 28, 2018https://github.com/PowerShell/PowerShell/issues/7557#issuecomment-442651313
Jason Shirk (@lzybkr)https://github.com/lzybkr
Steve Lee (SteveL-MSFT)https://github.com/SteveL-MSFT
Committee-ReviewedPS-Committee has reviewed this and made a decisionhttps://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22Committee-Reviewed%22
Review - CommitteeThe PR/Issue needs a review from the PowerShell Committeehttps://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22Review%20-%20Committee%22
on Nov 28, 2018https://github.com/PowerShell/PowerShell/issues/7557#event-1993903950
Travis Plunk (TravisEz13)https://github.com/TravisEz13
completedhttps://github.com/PowerShell/PowerShell/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
#7993https://github.com/PowerShell/PowerShell/pull/7993
on Apr 3, 2019https://github.com/PowerShell/PowerShell/issues/7557#event-2251259349
Travis Plunk (TravisEz13)https://github.com/TravisEz13
on Apr 3, 2019https://github.com/PowerShell/PowerShell/issues/7557#event-2251259708
Add Binary Parsing Support & Refactor TryGetNumberValue & ScanNumberH…https://github.com/PowerShell/PowerShell/commit/3f52adb0aeaf58189d85d386ab502e08f92ed41b
https://docs.github.com/articles/closing-issues-via-commit-messages
3f52adbhttps://github.com/PowerShell/PowerShell/commit/3f52adb0aeaf58189d85d386ab502e08f92ed41b
Ilya (iSazonov)https://github.com/iSazonov
Resolution-FixedThe issue is fixed.https://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22Resolution-Fixed%22
on Apr 4, 2019https://github.com/PowerShell/PowerShell/issues/7557#event-2251651020
Thatgfsj (Thatgfsj)https://github.com/Thatgfsj
on Aug 6, 2026https://github.com/PowerShell/PowerShell/issues/7557#event-29091204416
Add Binary Parsing Support & Refactor TryGetNumberValue & ScanNumberH…https://github.com/Thatgfsj-contribs/PowerShell/commit/273705d8b877990e5e0e9b9d5e7974b4bedb9698
https://docs.github.com/articles/closing-issues-via-commit-messages
273705dhttps://github.com/Thatgfsj-contribs/PowerShell/commit/273705d8b877990e5e0e9b9d5e7974b4bedb9698
Sign up for freehttps://github.com/signup?return_to=https://github.com/PowerShell/PowerShell/issues/7557
Sign in to commenthttps://github.com/login?return_to=https://github.com/PowerShell/PowerShell/issues/7557
Committee-ReviewedPS-Committee has reviewed this and made a decisionhttps://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22Committee-Reviewed%22
Issue-Enhancementthe issue is more of a feature request than a bughttps://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22Issue-Enhancement%22
Resolution-FixedThe issue is fixed.https://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22Resolution-Fixed%22
WG-Languageparser, language semanticshttps://github.com/PowerShell/PowerShell/issues?q=state%3Aopen%20label%3A%22WG-Language%22
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.