frontend: vectors and arrays no longer support in-memory coercion#25186
Merged
frontend: vectors and arrays no longer support in-memory coercion#25186
Conversation
andrewrk
added
breaking
it was always unnecessary but now it's illegal
Contributor
|
Is this what removed the ability to index vectors with runtime indices? |
Collaborator
|
no, that's #25154. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
closes #25172
Migration Guide
If you were using
@ptrCastto convert between array memory and vector memory, use coercion instead.If you were coercing from
anyerror![4]i32toanyerror!@Vector(4, i32)or similar, you need to unwrap the error first.