-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Inconsistent support for converting number strings with binary-multiplier / number-type suffixes to numbers #7710
Copy link
Copy link
Closed
Labels
Breaking-Changebreaking change that may affect usersbreaking change that may affect usersCommittee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionIssue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifResolution-FixedThe issue is fixed.The issue is fixed.Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Languageparser, language semanticsparser, language semantics
Metadata
Metadata
Assignees
Labels
Breaking-Changebreaking change that may affect usersbreaking change that may affect usersCommittee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionIssue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifResolution-FixedThe issue is fixed.The issue is fixed.Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Languageparser, language semanticsparser, language semantics
Type
Fields
Give feedbackNo fields configured for issues without a type.
Note:
When converting from strings,
PowerShell currently DOES recognize binary-multiplier suffixes such as
kb,mb, ...:'1gb' / 1)but DOES NOT recognize them:
during implicit type conversion in then context of parameter binding (e.g.,
& { param([int] $foo) } '1gb')(perhaps less surprisingly) in explicit type conversions with casts (e.g.,
[int] '1gb')Update: The same applies to PowerShell's number-data-type suffixes such as
dfor[decimal]andlfor[long].Environment data
Written as of: