[Version 9.0] Feature support for native sized integers (nint, and nuint)
#1457
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add support for native-sized integers Add support for native-sized integers Add support for native-sized integers Add support for native-sized integers Add support for native-sized integers Add support for native-sized integers Add support for native-sized integers Add support for native-sized integers fix example name correct link fix md formatting fix formatting fix md formatting made minor tweaks Add 2 new types make minor tweak Add native types to pointer indexing Update standard/expressions.md Co-authored-by: Kalle Olavi Niemitalo <[email protected]> Update standard/expressions.md Co-authored-by: Kalle Olavi Niemitalo <[email protected]> Add support for native-sized integers fix missing commit
BillWagner
changed the title
nint, and nuint)nint, and nuint)
RexJaeschke
reviewed
Nov 9, 2025
| ### 8.3.5 Simple types | ||
| C# provides a set of predefined `struct` types called the simple types. The simple types are identified through keywords, but these keywords are simply aliases for predefined `struct` types in the `System` namespace, as described in the table below. |
Contributor
There was a problem hiding this comment.
I struck the first sentence as this is already stated in 8.3.1.
Contributor
|
Can someone please check if changes should be made to §12.6.4.7. |
RexJaeschke
reviewed
Nov 9, 2025
Comment on lines
-2277
to
-2280
| - a value of an array type, the *element_access* is an array access ([§12.8.12.2](expressions.md#128122-array-access)); | ||
| - a value of `string` type, the *element_access* is a string access ([§12.8.12.3](expressions.md#128123-string-access)); | ||
| - otherwise, the *primary_expression* shall be a variable or value of a class, struct, or interface type that has one or more indexer members, in which case the *element_access* is an indexer access ([§12.8.12.4](expressions.md#128124-indexer-access)). | ||
Contributor
There was a problem hiding this comment.
These lines need to be restored. I have no idea how/why they were deleted.
RexJaeschke
reviewed
Nov 16, 2025
RexJaeschke
reviewed
Nov 16, 2025
RexJaeschke
reviewed
Nov 16, 2025
RexJaeschke
reviewed
Nov 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I wrote the bulk of this spec some years ago (based on the V9 MS proposal), and was happy with it. Then several years later, when I started looking at V11 features, I discovered that this topic was revisited (see V11 MS proposal). And I got confused as to which things should go in the V9 standard and which in the V11. Hopefully, I have it right now as far as V9 goes, but anyone reviewing this PR would do well to at least be conversant with how things will be changed in V11, to make sure the V9 spec is complete/correct. [Outside GitHub I have a Word document showing the expected changes for V11; ping me to get a copy (which Bill and Mads also have).] Rex
The commits from #1060 were squashed into one commit in this PR.
There are several comments on #1060 that need to be addressed: