RFC: Buffer and string slice syntax#222
Open
GameF200 wants to merge 2 commits into
Open
Conversation
Contributor
|
Just FYI, unfortunately buffer slices were already rejected: #163. I'd be interested in slicing with new range datatype constructed via concatting numbers though. local rang = 1..4
for i in rang do
end
local res = t[rang] |
Author
|
how would a slice metamethod even work? how would you make it follow the semantics of a slice? within the code example you provide, you just leave the function blank. |
Author
Oh, thats a tough question. I came up with __slice in the RFC just superficially. I think it's definitely worth reconsidering and standardizing somehow. |
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
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.
Rendered