Closed b5 closed 2 years ago
@b5 perfect, thank you
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.
We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent.
in this pull request.
Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla
label to yes
(if enabled on your project).
âšī¸ Googlers: Go here for more info.
@googlebot I consent
Sorry for the delay, I was very busy these days.
FYI I added a split function since in practice it is frequently used.
@b5 I believe that it is ready for a first review since I addressed everything that needed to be done so, could you please "un-draft it" đ
@adonovan Could you please review it? Thx in advance đ
@adonovan
This isn't correct: if the backslash is preceded by a backslash, then it should be legal. You will need to use a stripped down version of the scanning algorithm from the regexp package.
I double checked and unless I really missed your point, if I don't precede \C
with a backslash, I end up with the error invalid escape sequence \C
. I have just added two examples one with the patterns \d
, \w
and \s
all preceded by a backslash to show that it works as expected so the code seems to be actually correct (as you can see here).
Regarding the code, I only changed the code to use a raw string literal instead of a string literal to avoid having to escape the backslash but the logic is the same.
@brandjon could you please do the review đ ? @adonovan seems to be busy and/or not available
Sorry for the delay, will take a look presently.
@adonovan remarks addressed please check again
@adonovan remarks addressed and questions answered, please check again
@adonovan May I have a feedback please? đ
Let's get @brandjon to opine on the API before we go into details of the implementation.
Hi @brandjon, any feedbacks to give please đ ?
Let's try to finish it đ @brandjon Hi, thank you for your remarks, I've just pushed a new version, could you please check again đ ?
@brandjon Could you please check again? đ
@adonovan @brandjon any remarks about this PR?
Any update here folks?
Checking back a year later đ any update here? Is this PR blocked by something?
@luispadron yes this PR is blocked because unfortunately there is no more reviewers in this project đ
@luispadron I guess we need to consider that this project is in maintenance mode and no more features will be accepted
@b5 I guess you can close it
Dang. Frustrating. Ok closing now
@luispadron I guess we need to consider that this project is in maintenance mode and no more features will be accepted
So is this project dead now?
No, Starlark-go is very much alive, but time is precious and a regexp package is nowhere near our highest priorities. I'd still be willing to approve a PR to add the right API, but I don't know what that looks like at the moment and it would be a shame to add something that is too closely coupled to the underlying Go implementation to be implemented in Java or -Rust (as we may have done with the time package).
Until such time as a standard regexp package is added, you can of course fork the code in this PR in your own project.
Is there any plan of adding regexp to starlark anytime soon ?
@essobedo is going to be heading up turning this code into a package that closes #241. We're using the
re
package from starlib as a starting point, but it needs a lot of work before it's ready for initial review.@essobedo I think at a minimum we should:
regexp/doc.go
(I've kept it only so you have context)regexp/regexp.go
\C