-
Notifications
You must be signed in to change notification settings - Fork 437
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: rust-lang/regex
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 1.10.6
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: rust-lang/regex
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.11.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 11 commits
- 28 files changed
- 2 contributors
Commits on Sep 29, 2024
-
automata: add explicit lifetime annotation
rustc seems to warn about this. And I would prefer writing the lifetime here anyway. That it wasn't was probably an oversight.
Configuration menu - View commit details
-
Copy full SHA for 92efe4a - Browse repository at this point
Copy the full SHA 92efe4aView commit details -
It looks like rustc picks this up now but didn't before.
Configuration menu - View commit details
-
Copy full SHA for d3d3ff7 - Browse repository at this point
Copy the full SHA d3d3ff7View commit details -
api: add SetMatches::matched_all
This complements `matched_any` with a means to check if a set of patterns all matched the haystack. PR #1228
Configuration menu - View commit details
-
Copy full SHA for b790aa5 - Browse repository at this point
Copy the full SHA b790aa5View commit details -
cli: include \w, \s and \d in Unicode data table generation
This was an oversight omission when porting the old generator shell script to regex-cli. This hasn't been an issue because I don't think we've generated data for a new release of Unicode with this new infrastructure yet. This was flagged by unit tests that failed because \d was no longer a subset of \w.
Configuration menu - View commit details
-
Copy full SHA for 7691e49 - Browse repository at this point
Copy the full SHA 7691e49View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9239e7e - Browse repository at this point
Copy the full SHA 9239e7eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1533257 - Browse repository at this point
Copy the full SHA 1533257View commit details -
Configuration menu - View commit details
-
Copy full SHA for cba0fbc - Browse repository at this point
Copy the full SHA cba0fbcView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4bb1e3d - Browse repository at this point
Copy the full SHA 4bb1e3dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 58e16f5 - Browse repository at this point
Copy the full SHA 58e16f5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9e17e56 - Browse repository at this point
Copy the full SHA 9e17e56View commit details -
Configuration menu - View commit details
-
Copy full SHA for bcbe403 - Browse repository at this point
Copy the full SHA bcbe403View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 1.10.6...1.11.0