Skip to content

Conversation

@luochuanhang
Copy link
Contributor

@luochuanhang luochuanhang commented Jan 17, 2022

No description provided.

@gopherbot
Copy link
Contributor

This PR (HEAD: d1d668a) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/378935 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://golang.org/doc/contribute.html#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11 or adds a tag like "wait-release", it means that this CL will be
reviewed as part of the next development cycle. See https://golang.org/s/release
for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/378935.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ian Lance Taylor:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/378935.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Brad Fitzpatrick:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/378935.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Daniel Martí:

Patch Set 2:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/378935.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from luo chuanhang:

Patch Set 3:

(2 comments)


Please don’t reply on this GitHub thread. Visit golang.org/cl/378935.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ian Lance Taylor:

Patch Set 3: Code-Review+2


Please don’t reply on this GitHub thread. Visit golang.org/cl/378935.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Daniel Martí:

Patch Set 3: Trust+1


Please don’t reply on this GitHub thread. Visit golang.org/cl/378935.
After addressing review feedback, remember to publish your drafts!

gopherbot pushed a commit that referenced this pull request Jan 19, 2022
Change-Id: I23264972329aa3414067cd0e0986b69bb39bbeb5
GitHub-Last-Rev: d1d668a
GitHub-Pull-Request: #50650
Reviewed-on: https://go-review.googlesource.com/c/go/+/378935
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Trust: Daniel Martí <mvdan@mvdan.cc>
@gopherbot
Copy link
Contributor

This PR is being closed because golang.org/cl/378935 has been merged.

@gopherbot gopherbot closed this Jan 19, 2022
jproberts pushed a commit to jproberts/go that referenced this pull request Jun 21, 2022
Change-Id: I23264972329aa3414067cd0e0986b69bb39bbeb5
GitHub-Last-Rev: d1d668a
GitHub-Pull-Request: golang#50650
Reviewed-on: https://go-review.googlesource.com/c/go/+/378935
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Trust: Daniel Martí <mvdan@mvdan.cc>
gopherbot pushed a commit to golang/oscar that referenced this pull request Oct 6, 2025
text-embedding-004 is deprecated and will stop working in January 2026,
so switch to gemini-embedding-001.

The results are better in some ways and worse in others.
They should work about the same for the related issues feature,
although we may want to adjust the thresholds after a few days
of seeing how the new embeddings do for real usage.

Before:

> regexp issue about adding iterators
^D

 0.67100 golang/go#61902 # proposal: regexp: add iterator forms of matching methods
 0.67000 golang/go#351 # Regexp can't handle lazy quantifiers
 0.66900 golang/go#43332 # regexp: Repeated capture groups only capturing final captured match.
 0.66300 golang/go#64108 # regexp: Documentation doesn't mention that (?<name>...) capturing group syntax isn't currently supported
 0.65500 golang/go#56507 # regexp: improve Regexp.ReplaceAll documentation and tests related to Expand part

> proposal: regexp: add iterator forms of matching methods
^D

 0.75600 golang/go#61902 # proposal: regexp: add iterator forms of matching methods
 0.67000 golang/go#21463 # proposal: regexp: Optimize fixed-length patterns
 0.66700 golang/go#54047 # proposal: Go 2: add a new iterator syntax, package, interfaces
 0.66100 golang/go#43557 # proposal: Go 2: function values as iterators
 0.65500 golang/go#65742 # proposal: Go 2: range-over-function + range over types implementing iterator interface

> We propose to add methods to regexp that allow iterating over matches instead of having to accumulate all the matches into a slice.

This is one of a collection of proposals updating the standard library for the new 'range over function' feature (#61405). It would only be accepted if that proposal is accepted. See golang/oscar#61897 for a list of related proposals.

Regexp has a lot of methods that return slices of all matches (the “FindAll*” methods). Each should have an iterator equivalent that doesn’t build the slice. They can be named by removing the “Find” prefix. The docs would change as follows. (Plain text is unchanged; strikethrough is removed, bold is added):
^D

 0.86400 golang/go#61902 # proposal: regexp: add iterator forms of matching methods
 0.71700 https://go.dev/wiki/RangefuncExperiment#can-you-provide-more-motivation-for-range-over-functions # Go Wiki: Rangefunc Experiment > Can you provide more motivation for range over functions?
 0.69100 golang/go#61901 # bytes, strings: add iterator forms of existing functions
 0.68800 golang/go#61899 # slices: add iterator-related functions
 0.68200 https://go.dev/pkg/regexp/?m=old#Regexp.FindAll # Package regexp > type Regexp > func (*Regexp) FindAll

After:

> regexp issue about adding iterators
^D

 0.76400 golang/go#50650 # regexp: add the missing is
 0.71900 golang/go#17146 # How about add MatchStrings() in regexp meet match string more than one?
 0.71200 golang/go#56973 # regexp: add comment in example test describing tricky behavior
 0.69700 golang/go#61902 # proposal: regexp: add iterator forms of matching methods
 0.69500 golang/go#63350 # regexp/syntax: use min func

> proposal: regexp: add iterator forms of matching methods
^D

 0.87400 golang/go#61902 # proposal: regexp: add iterator forms of matching methods
 0.77400 golang/go#61901 # bytes, strings: add iterator forms of existing functions
 0.76400 golang/go#24208 # proposal: regexp: Add functions to the Regexp type to ease accessing named capture groups
 0.76300 golang/go#32881 # regexp: Named captures should appear in a hashmap
 0.76000 golang/go#66631 # proposal: reflect: Add Type.Fields() iter.Seq[StructField] and Type.Methods() iter.Seq[Method]

> We propose to add methods to regexp that allow iterating over matches instead of having to accumulate all the matches into a slice.

This is one of a collection of proposals updating the standard library for the new 'range over function' feature (#61405). It would only be accepted if that proposal is accepted. See golang/oscar#61897 for a list of related proposals.

Regexp has a lot of methods that return slices of all matches (the “FindAll*” methods). Each should have an iterator equivalent that doesn’t build the slice. They can be named by removing the “Find” prefix. The docs would change as follows. (Plain text is unchanged; strikethrough is removed, bold is added):
^D

 0.94900 golang/go#61902 # proposal: regexp: add iterator forms of matching methods
 0.86200 golang/go#61901 # bytes, strings: add iterator forms of existing functions
 0.83600 golang/go#61899 # slices: add iterator-related functions
 0.83100 golang/go#61897 # iter: new package for iterators
 0.81100 golang/go#62113 # proposal: x/net/html: add Node.All(), Node.ChildNodes(), Nodes.Parents() iterators

Change-Id: Ic6ce353588b62ba7bae12562378b012d18e5feb2
Reviewed-on: https://go-review.googlesource.com/c/oscar/+/708880
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Tatiana Bradley <tatianabradley@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants