Repository navigation
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: BurntSushi/aho-corasick
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0.7.15
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: BurntSushi/aho-corasick
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 0.7.18
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 9 commits
- 29 files changed
- 1 contributor
Commits on Apr 30, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 45a4ee7 - Browse repository at this point
Copy the full SHA 45a4ee7View commit details -
Configuration menu - View commit details
-
Copy full SHA for b253580 - Browse repository at this point
Copy the full SHA b253580View commit details -
Configuration menu - View commit details
-
Copy full SHA for c3136f1 - Browse repository at this point
Copy the full SHA c3136f1View commit details -
api: deprecate byte classes and premultiply options
These options aren't really carrying their weight. In a future release, aho-corasick will make both options enabled by default all the time with the impossibility of disabling them. The main reason for this is that these options require a quadrupling in the amount of code in this crate. While it's possible to see a performance hit when using byte classes, it should generally be very small. The improvement, if one exists, just doesn't see worth it. Please see #57 for more discussion. This is meant to mirror a similar decision occurring in regex-automata: BurntSushi/regex-automata#7.
Configuration menu - View commit details
-
Copy full SHA for 04e8c74 - Browse repository at this point
Copy the full SHA 04e8c74View commit details -
This is in line with similar changes to the regex and memchr crates: BurntSushi/memchr#82 and rust-lang/regex#767
Configuration menu - View commit details
-
Copy full SHA for b149915 - Browse repository at this point
Copy the full SHA b149915View commit details -
We also use the 'std' feature in lieu of the 'use_std' feature, which was deprecated quite some time ago.
Configuration menu - View commit details
-
Copy full SHA for 2281bf6 - Browse repository at this point
Copy the full SHA 2281bf6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 33c6522 - Browse repository at this point
Copy the full SHA 33c6522View commit details -
build: fix compilation on i686
It looks like 'cargo fix' didn't quite fix all 'use' statements.
Configuration menu - View commit details
-
Copy full SHA for 8ac8f73 - Browse repository at this point
Copy the full SHA 8ac8f73View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1b11637 - Browse repository at this point
Copy the full SHA 1b11637View 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 0.7.15...0.7.18