Skip to content

issue with array initialization using index #23224

Discussion options

You must be logged in to vote

For now, i32 and int should be treated the same. int is supposed to be changed at some point so it will either be i32 or i64, depending on the system.

In any case, this is a bug. index should always be the correct type to init the array, not a fixed int.

#23225

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by Lord-Vlad
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants