rust/ripgrep
1
0
Fork 0
mirror of https://github.com/BurntSushi/ripgrep.git synced 2024-12-12 19:18:24 +02:00
Code Issues Releases Activity
7923d25228
ripgrep/Cargo.lock

623 lines
14 KiB
Plaintext
Raw Normal View History

cargo: include auto-generated message This is going to be annoying for a while if one switches between the latest nightly compiler and older compilers. Sigh.
2019-01-29 20:04:40 +02:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
deps: bump regex and regex-syntax
2021-03-12 04:20:25 +02:00
version = 3
deps: update everything This updates all dependencies to their latest versions. We tolerate a duplicative aho-corasick for now, which we will fix in the next commit.
2019-04-03 19:07:26 +02:00
[[package]]
name = "aho-corasick"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "0.7.15"
deps: update everything This updates all dependencies to their latest versions. We tolerate a duplicative aho-corasick for now, which we will fix in the next commit.
2019-04-03 19:07:26 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "7404febffaa47dac81aa44dba71523c9d069b1bdc50a77db41195149e17f68e5"
deps: update everything This updates all dependencies to their latest versions. We tolerate a duplicative aho-corasick for now, which we will fix in the next commit.
2019-04-03 19:07:26 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"memchr",
deps: update everything This updates all dependencies to their latest versions. We tolerate a duplicative aho-corasick for now, which we will fix in the next commit.
2019-04-03 19:07:26 +02:00
]
Replace internal atty module with atty crate. This removes all use of explicit unsafe in ripgrep proper except for one: accessing the contents of a memory map. (Which may never go away.)
2017-01-15 23:32:30 +02:00
[[package]]
name = "atty"
deps: run cargo update The only new dependency is an unused target specific dependency hermit via the atty crate.
2020-01-10 03:38:00 +02:00
version = "0.2.14"
Replace internal atty module with atty crate. This removes all use of explicit unsafe in ripgrep proper except for one: accessing the contents of a memory map. (Which may never go away.)
2017-01-15 23:32:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
Replace internal atty module with atty crate. This removes all use of explicit unsafe in ripgrep proper except for one: accessing the contents of a memory map. (Which may never go away.)
2017-01-15 23:32:30 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"hermit-abi",
"libc",
"winapi",
Replace internal atty module with atty crate. This removes all use of explicit unsafe in ripgrep proper except for one: accessing the contents of a memory map. (Which may never go away.)
2017-01-15 23:32:30 +02:00
]
deps: update to crossbeam-channel 0.4 Closes #1427
2020-01-10 04:10:14 +02:00
[[package]]
name = "autocfg"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
version = "1.0.1"
deps: update to crossbeam-channel 0.4 Closes #1427
2020-01-10 04:10:14 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
checksum = "cdb031dd78e28731d87d56cc8ffef4a8f36ca26c38fe2de700543e627f8a464a"
deps: update to crossbeam-channel 0.4 Closes #1427
2020-01-10 04:10:14 +02:00
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "base64"
deps: update base64 to 0.13.0
2020-11-02 17:07:59 +02:00
version = "0.13.0"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update base64 to 0.13.0
2020-11-02 17:07:59 +02:00
checksum = "904dfeac50f3cdaba28fc6f57fdcddb75f49ed61346676a78c4ffe55877802fd"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
[[package]]
name = "bitflags"
deps: run cargo update The only new dependency is an unused target specific dependency hermit via the atty crate.
2020-01-10 03:38:00 +02:00
version = "1.2.1"
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "cf1de2fe8c75bc145a2f577add951f8134889b4795d47466a54a5c846d691693"
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
deps: add bstr to Cargo.lock
2019-04-06 04:28:43 +02:00
[[package]]
name = "bstr"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
version = "0.2.14"
deps: add bstr to Cargo.lock
2019-04-06 04:28:43 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
checksum = "473fc6b38233f9af7baa94fb5852dca389e3d95b8e21c8e3719301462c5d9faf"
deps: add bstr to Cargo.lock
2019-04-06 04:28:43 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"lazy_static",
"memchr",
"regex-automata",
deps: add bstr to Cargo.lock
2019-04-06 04:28:43 +02:00
]
Use the bytecount crate for fast line counting. Fixes #128
2016-09-23 04:59:25 +02:00
[[package]]
name = "bytecount"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "0.6.2"
Use the bytecount crate for fast line counting. Fixes #128
2016-09-23 04:59:25 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "72feb31ffc86498dacdbd0fcebb56138e7177a8cc5cea4516031d15ae85a742e"
Use the bytecount crate for fast line counting. Fixes #128
2016-09-23 04:59:25 +02:00
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "byteorder"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "1.4.2"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "ae44d1a3d5a19df61dd0c8beb138458ac2a53a7ac09eba97d55592540004306b"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "cc"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "1.0.66"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "4c0496836a84f8d0495758516b8621a622beb77c0fed418570e50764093ced48"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
dependencies = [
"jobserver",
]
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
Add support for additional text encodings. This includes, but is not limited to, UTF-16, latin-1, GBK, EUC-JP and Shift_JIS. (Courtesy of the `encoding_rs` crate.) Specifically, this feature enables ripgrep to search files that are encoded in an encoding other than UTF-8. The list of available encodings is tied directly to what the `encoding_rs` crate supports, which is in turn tied to the Encoding Standard. The full list of available encodings can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get This pull request also introduces the notion that text encodings can be automatically detected on a best effort basis. Currently, the only support for this is checking for a UTF-16 bom. In all other cases, a text encoding of `auto` (the default) implies a UTF-8 or ASCII compatible source encoding. When a text encoding is otherwise specified, it is unconditionally used for all files searched. Since ripgrep's regex engine is fundamentally built on top of UTF-8, this feature works by transcoding the files to be searched from their source encoding to UTF-8. This transcoding only happens when: 1. `auto` is specified and a non-UTF-8 encoding is detected. 2. A specific encoding is given by end users (including UTF-8). When transcoding occurs, errors are handled by automatically inserting the Unicode replacement character. In this case, ripgrep's output is guaranteed to be valid UTF-8 (excluding non-UTF-8 file paths, if they are printed). In all other cases, the source text is searched directly, which implies an assumption that it is at least ASCII compatible, but where UTF-8 is most useful. In this scenario, encoding errors are not detected. In this case, ripgrep's output will match the input exactly, byte-for-byte. This design may not be optimal in all cases, but it has some advantages: 1. In the happy path ("UTF-8 everywhere") remains happy. I have not been able to witness any performance regressions. 2. In the non-UTF-8 path, implementation complexity is kept relatively low. The cost here is transcoding itself. A potentially superior implementation might build decoding of any encoding into the regex engine itself. In particular, the fundamental problem with transcoding everything first is that literal optimizations are nearly negated. Future work should entail improving the user experience. For example, we might want to auto-detect more text encodings. A more elaborate UX experience might permit end users to specify multiple text encodings, although this seems hard to pull off in an ergonomic way. Fixes #1
2017-03-09 03:22:48 +02:00
[[package]]
name = "cfg-if"
deps: run cargo update The only new dependency is an unused target specific dependency hermit via the atty crate.
2020-01-10 03:38:00 +02:00
version = "0.1.10"
Add support for additional text encodings. This includes, but is not limited to, UTF-16, latin-1, GBK, EUC-JP and Shift_JIS. (Courtesy of the `encoding_rs` crate.) Specifically, this feature enables ripgrep to search files that are encoded in an encoding other than UTF-8. The list of available encodings is tied directly to what the `encoding_rs` crate supports, which is in turn tied to the Encoding Standard. The full list of available encodings can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get This pull request also introduces the notion that text encodings can be automatically detected on a best effort basis. Currently, the only support for this is checking for a UTF-16 bom. In all other cases, a text encoding of `auto` (the default) implies a UTF-8 or ASCII compatible source encoding. When a text encoding is otherwise specified, it is unconditionally used for all files searched. Since ripgrep's regex engine is fundamentally built on top of UTF-8, this feature works by transcoding the files to be searched from their source encoding to UTF-8. This transcoding only happens when: 1. `auto` is specified and a non-UTF-8 encoding is detected. 2. A specific encoding is given by end users (including UTF-8). When transcoding occurs, errors are handled by automatically inserting the Unicode replacement character. In this case, ripgrep's output is guaranteed to be valid UTF-8 (excluding non-UTF-8 file paths, if they are printed). In all other cases, the source text is searched directly, which implies an assumption that it is at least ASCII compatible, but where UTF-8 is most useful. In this scenario, encoding errors are not detected. In this case, ripgrep's output will match the input exactly, byte-for-byte. This design may not be optimal in all cases, but it has some advantages: 1. In the happy path ("UTF-8 everywhere") remains happy. I have not been able to witness any performance regressions. 2. In the non-UTF-8 path, implementation complexity is kept relatively low. The cost here is transcoding itself. A potentially superior implementation might build decoding of any encoding into the regex engine itself. In particular, the fundamental problem with transcoding everything first is that literal optimizations are nearly negated. Future work should entail improving the user experience. For example, we might want to auto-detect more text encodings. A more elaborate UX experience might permit end users to specify multiple text encodings, although this seems hard to pull off in an ergonomic way. Fixes #1
2017-03-09 03:22:48 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
Add support for additional text encodings. This includes, but is not limited to, UTF-16, latin-1, GBK, EUC-JP and Shift_JIS. (Courtesy of the `encoding_rs` crate.) Specifically, this feature enables ripgrep to search files that are encoded in an encoding other than UTF-8. The list of available encodings is tied directly to what the `encoding_rs` crate supports, which is in turn tied to the Encoding Standard. The full list of available encodings can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get This pull request also introduces the notion that text encodings can be automatically detected on a best effort basis. Currently, the only support for this is checking for a UTF-16 bom. In all other cases, a text encoding of `auto` (the default) implies a UTF-8 or ASCII compatible source encoding. When a text encoding is otherwise specified, it is unconditionally used for all files searched. Since ripgrep's regex engine is fundamentally built on top of UTF-8, this feature works by transcoding the files to be searched from their source encoding to UTF-8. This transcoding only happens when: 1. `auto` is specified and a non-UTF-8 encoding is detected. 2. A specific encoding is given by end users (including UTF-8). When transcoding occurs, errors are handled by automatically inserting the Unicode replacement character. In this case, ripgrep's output is guaranteed to be valid UTF-8 (excluding non-UTF-8 file paths, if they are printed). In all other cases, the source text is searched directly, which implies an assumption that it is at least ASCII compatible, but where UTF-8 is most useful. In this scenario, encoding errors are not detected. In this case, ripgrep's output will match the input exactly, byte-for-byte. This design may not be optimal in all cases, but it has some advantages: 1. In the happy path ("UTF-8 everywhere") remains happy. I have not been able to witness any performance regressions. 2. In the non-UTF-8 path, implementation complexity is kept relatively low. The cost here is transcoding itself. A potentially superior implementation might build decoding of any encoding into the regex engine itself. In particular, the fundamental problem with transcoding everything first is that literal optimizations are nearly negated. Future work should entail improving the user experience. For example, we might want to auto-detect more text encodings. A more elaborate UX experience might permit end users to specify multiple text encodings, although this seems hard to pull off in an ergonomic way. Fixes #1
2017-03-09 03:22:48 +02:00
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
[[package]]
name = "clap"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
version = "2.33.3"
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
checksum = "37e58ac78573c40708d45522f0d80fa2f01cc4f9b4e2bf749807255454312002"
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"bitflags",
"strsim",
"textwrap",
"unicode-width",
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
]
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
[[package]]
name = "crossbeam-channel"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dca26ee1f8d361640700bde38b2c37d8c22b3ce2d360e1fc1c74ea4b0aa7d775"
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
dependencies = [
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
"cfg-if 1.0.0",
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"crossbeam-utils",
ripgrep: move minimum version to Rust stable This also updates some code to make use of our more liberal versioning requirement, including the use of crossbeam-channel instead of the MsQueue from the older an unmaintained crossbeam 0.3. This does regrettably add a sizable number of dependencies, however, compile times seem mostly unaffected. Closes #1019
2018-08-22 01:47:12 +02:00
]
[[package]]
name = "crossbeam-utils"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "0.8.1"
Add parallel recursive directory iterator. This adds a new walk type in the `ignore` crate, `WalkParallel`, which provides a way for recursively iterating over a set of paths in parallel while respecting various ignore rules. The API is a bit strange, as a closure producing a closure isn't something one often sees, but it does seem to work well. This also allowed us to simplify much of the worker logic in ripgrep proper, where MultiWorker is now gone.
2016-11-06 03:44:15 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "02d96d1e189ef58269ebe5b97953da3274d83a93af647c2ddd6f9dab28cedb8d"
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"autocfg",
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
"cfg-if 1.0.0",
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"lazy_static",
deps: update to crossbeam-channel 0.3 This also requires corresponding updates to both rand and rand_core. Doing an update of rand without doing an update of rand_core results in compilation errors because two distinct versions of rand_core are included in the build, and the traits they expose are distinct and incompatible. We also switch over to using tempfile instead of tempdir, which drops the last remaining thing keeping rand 0.4 in the build. Fixes #1141, Fixes #1142
2018-12-15 15:37:52 +02:00
]
Add parallel recursive directory iterator. This adds a new walk type in the `ignore` crate, `WalkParallel`, which provides a way for recursively iterating over a set of paths in parallel while respecting various ignore rules. The API is a bit strange, as a closure producing a closure isn't something one often sees, but it does seem to work well. This also allowed us to simplify much of the worker logic in ripgrep proper, where MultiWorker is now gone.
2016-11-06 03:44:15 +02:00
Add support for additional text encodings. This includes, but is not limited to, UTF-16, latin-1, GBK, EUC-JP and Shift_JIS. (Courtesy of the `encoding_rs` crate.) Specifically, this feature enables ripgrep to search files that are encoded in an encoding other than UTF-8. The list of available encodings is tied directly to what the `encoding_rs` crate supports, which is in turn tied to the Encoding Standard. The full list of available encodings can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get This pull request also introduces the notion that text encodings can be automatically detected on a best effort basis. Currently, the only support for this is checking for a UTF-16 bom. In all other cases, a text encoding of `auto` (the default) implies a UTF-8 or ASCII compatible source encoding. When a text encoding is otherwise specified, it is unconditionally used for all files searched. Since ripgrep's regex engine is fundamentally built on top of UTF-8, this feature works by transcoding the files to be searched from their source encoding to UTF-8. This transcoding only happens when: 1. `auto` is specified and a non-UTF-8 encoding is detected. 2. A specific encoding is given by end users (including UTF-8). When transcoding occurs, errors are handled by automatically inserting the Unicode replacement character. In this case, ripgrep's output is guaranteed to be valid UTF-8 (excluding non-UTF-8 file paths, if they are printed). In all other cases, the source text is searched directly, which implies an assumption that it is at least ASCII compatible, but where UTF-8 is most useful. In this scenario, encoding errors are not detected. In this case, ripgrep's output will match the input exactly, byte-for-byte. This design may not be optimal in all cases, but it has some advantages: 1. In the happy path ("UTF-8 everywhere") remains happy. I have not been able to witness any performance regressions. 2. In the non-UTF-8 path, implementation complexity is kept relatively low. The cost here is transcoding itself. A potentially superior implementation might build decoding of any encoding into the regex engine itself. In particular, the fundamental problem with transcoding everything first is that literal optimizations are nearly negated. Future work should entail improving the user experience. For example, we might want to auto-detect more text encodings. A more elaborate UX experience might permit end users to specify multiple text encodings, although this seems hard to pull off in an ergonomic way. Fixes #1
2017-03-09 03:22:48 +02:00
[[package]]
name = "encoding_rs"
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
version = "0.8.26"
Add support for additional text encodings. This includes, but is not limited to, UTF-16, latin-1, GBK, EUC-JP and Shift_JIS. (Courtesy of the `encoding_rs` crate.) Specifically, this feature enables ripgrep to search files that are encoded in an encoding other than UTF-8. The list of available encodings is tied directly to what the `encoding_rs` crate supports, which is in turn tied to the Encoding Standard. The full list of available encodings can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get This pull request also introduces the notion that text encodings can be automatically detected on a best effort basis. Currently, the only support for this is checking for a UTF-16 bom. In all other cases, a text encoding of `auto` (the default) implies a UTF-8 or ASCII compatible source encoding. When a text encoding is otherwise specified, it is unconditionally used for all files searched. Since ripgrep's regex engine is fundamentally built on top of UTF-8, this feature works by transcoding the files to be searched from their source encoding to UTF-8. This transcoding only happens when: 1. `auto` is specified and a non-UTF-8 encoding is detected. 2. A specific encoding is given by end users (including UTF-8). When transcoding occurs, errors are handled by automatically inserting the Unicode replacement character. In this case, ripgrep's output is guaranteed to be valid UTF-8 (excluding non-UTF-8 file paths, if they are printed). In all other cases, the source text is searched directly, which implies an assumption that it is at least ASCII compatible, but where UTF-8 is most useful. In this scenario, encoding errors are not detected. In this case, ripgrep's output will match the input exactly, byte-for-byte. This design may not be optimal in all cases, but it has some advantages: 1. In the happy path ("UTF-8 everywhere") remains happy. I have not been able to witness any performance regressions. 2. In the non-UTF-8 path, implementation complexity is kept relatively low. The cost here is transcoding itself. A potentially superior implementation might build decoding of any encoding into the regex engine itself. In particular, the fundamental problem with transcoding everything first is that literal optimizations are nearly negated. Future work should entail improving the user experience. For example, we might want to auto-detect more text encodings. A more elaborate UX experience might permit end users to specify multiple text encodings, although this seems hard to pull off in an ergonomic way. Fixes #1
2017-03-09 03:22:48 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
checksum = "801bbab217d7f79c0062f4f7205b5d4427c6d1a7bd7aafdd1475f7c59d62b283"
Add support for additional text encodings. This includes, but is not limited to, UTF-16, latin-1, GBK, EUC-JP and Shift_JIS. (Courtesy of the `encoding_rs` crate.) Specifically, this feature enables ripgrep to search files that are encoded in an encoding other than UTF-8. The list of available encodings is tied directly to what the `encoding_rs` crate supports, which is in turn tied to the Encoding Standard. The full list of available encodings can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get This pull request also introduces the notion that text encodings can be automatically detected on a best effort basis. Currently, the only support for this is checking for a UTF-16 bom. In all other cases, a text encoding of `auto` (the default) implies a UTF-8 or ASCII compatible source encoding. When a text encoding is otherwise specified, it is unconditionally used for all files searched. Since ripgrep's regex engine is fundamentally built on top of UTF-8, this feature works by transcoding the files to be searched from their source encoding to UTF-8. This transcoding only happens when: 1. `auto` is specified and a non-UTF-8 encoding is detected. 2. A specific encoding is given by end users (including UTF-8). When transcoding occurs, errors are handled by automatically inserting the Unicode replacement character. In this case, ripgrep's output is guaranteed to be valid UTF-8 (excluding non-UTF-8 file paths, if they are printed). In all other cases, the source text is searched directly, which implies an assumption that it is at least ASCII compatible, but where UTF-8 is most useful. In this scenario, encoding errors are not detected. In this case, ripgrep's output will match the input exactly, byte-for-byte. This design may not be optimal in all cases, but it has some advantages: 1. In the happy path ("UTF-8 everywhere") remains happy. I have not been able to witness any performance regressions. 2. In the non-UTF-8 path, implementation complexity is kept relatively low. The cost here is transcoding itself. A potentially superior implementation might build decoding of any encoding into the regex engine itself. In particular, the fundamental problem with transcoding everything first is that literal optimizations are nearly negated. Future work should entail improving the user experience. For example, we might want to auto-detect more text encodings. A more elaborate UX experience might permit end users to specify multiple text encodings, although this seems hard to pull off in an ergonomic way. Fixes #1
2017-03-09 03:22:48 +02:00
dependencies = [
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
"cfg-if 1.0.0",
"packed_simd_2",
Add support for additional text encodings. This includes, but is not limited to, UTF-16, latin-1, GBK, EUC-JP and Shift_JIS. (Courtesy of the `encoding_rs` crate.) Specifically, this feature enables ripgrep to search files that are encoded in an encoding other than UTF-8. The list of available encodings is tied directly to what the `encoding_rs` crate supports, which is in turn tied to the Encoding Standard. The full list of available encodings can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get This pull request also introduces the notion that text encodings can be automatically detected on a best effort basis. Currently, the only support for this is checking for a UTF-16 bom. In all other cases, a text encoding of `auto` (the default) implies a UTF-8 or ASCII compatible source encoding. When a text encoding is otherwise specified, it is unconditionally used for all files searched. Since ripgrep's regex engine is fundamentally built on top of UTF-8, this feature works by transcoding the files to be searched from their source encoding to UTF-8. This transcoding only happens when: 1. `auto` is specified and a non-UTF-8 encoding is detected. 2. A specific encoding is given by end users (including UTF-8). When transcoding occurs, errors are handled by automatically inserting the Unicode replacement character. In this case, ripgrep's output is guaranteed to be valid UTF-8 (excluding non-UTF-8 file paths, if they are printed). In all other cases, the source text is searched directly, which implies an assumption that it is at least ASCII compatible, but where UTF-8 is most useful. In this scenario, encoding errors are not detected. In this case, ripgrep's output will match the input exactly, byte-for-byte. This design may not be optimal in all cases, but it has some advantages: 1. In the happy path ("UTF-8 everywhere") remains happy. I have not been able to witness any performance regressions. 2. In the non-UTF-8 path, implementation complexity is kept relatively low. The cost here is transcoding itself. A potentially superior implementation might build decoding of any encoding into the regex engine itself. In particular, the fundamental problem with transcoding everything first is that literal optimizations are nearly negated. Future work should entail improving the user experience. For example, we might want to auto-detect more text encodings. A more elaborate UX experience might permit end users to specify multiple text encodings, although this seems hard to pull off in an ergonomic way. Fixes #1
2017-03-09 03:22:48 +02:00
]
ripgrep: replace decoder with encoding_rs_io This commit mostly moves the transcoder implementation to its own crate: https://github.com/BurntSushi/encoding_rs_io The new crate adds clear documentation and cleans up the implementation to fully implement the contract of io::Read.
2018-07-22 02:36:32 +02:00
[[package]]
name = "encoding_rs_io"
deps: update everything This adds one new dependency, maybe-uninit, which is brought in by crossbeam-channel[1]. This is to apparently fix some unsound code without bumping the MSRV. Since ripgrep uses the latest stable release of Rust, the maybe-uninit crate should compile down to nothing and just re-export std's `MaybeUninit` type. [1] - https://github.com/crossbeam-rs/crossbeam/pull/458
2020-03-15 14:32:33 +02:00
version = "0.1.7"
ripgrep: replace decoder with encoding_rs_io This commit mostly moves the transcoder implementation to its own crate: https://github.com/BurntSushi/encoding_rs_io The new crate adds clear documentation and cleans up the implementation to fully implement the contract of io::Read.
2018-07-22 02:36:32 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "1cc3c5651fb62ab8aa3103998dade57efdd028544bd300516baa31840c252a83"
ripgrep: replace decoder with encoding_rs_io This commit mostly moves the transcoder implementation to its own crate: https://github.com/BurntSushi/encoding_rs_io The new crate adds clear documentation and cleans up the implementation to fully implement the contract of io::Read.
2018-07-22 02:36:32 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"encoding_rs",
ripgrep: replace decoder with encoding_rs_io This commit mostly moves the transcoder implementation to its own crate: https://github.com/BurntSushi/encoding_rs_io The new crate adds clear documentation and cleans up the implementation to fully implement the contract of io::Read.
2018-07-22 02:36:32 +02:00
]
Rework glob sets. We try to reduce the pressure on regexes and offload some of it to Aho-Corasick or exact lookups.
2016-09-16 04:06:04 +02:00
[[package]]
name = "fnv"
deps: update all dependencies
2020-05-29 15:11:50 +02:00
version = "1.0.7"
Rework glob sets. We try to reduce the pressure on regexes and offload some of it to Aho-Corasick or exact lookups.
2016-09-16 04:06:04 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
Rework glob sets. We try to reduce the pressure on regexes and offload some of it to Aho-Corasick or exact lookups.
2016-09-16 04:06:04 +02:00
alloc: use jemalloc when building with musl It turns out that musl's allocator is slow enough to cause a fairly noticeable performance regression when ripgrep is built as a static binary with musl. We fix this by using jemalloc when building with musl. We continue to use the default system allocator in all other scenarios. Namely, glibc's allocator doesn't noticeably regress performance compared to jemalloc. But we could add more targets to this logic if other system allocators (macOS, Windows) prove to be slow. This wasn't necessary before because rustc recently stopped using jemalloc by default. Fixes #1268
2019-04-24 23:21:38 +02:00
[[package]]
name = "fs_extra"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
version = "1.2.0"
alloc: use jemalloc when building with musl It turns out that musl's allocator is slow enough to cause a fairly noticeable performance regression when ripgrep is built as a static binary with musl. We fix this by using jemalloc when building with musl. We continue to use the default system allocator in all other scenarios. Namely, glibc's allocator doesn't noticeably regress performance compared to jemalloc. But we could add more targets to this logic if other system allocators (macOS, Windows) prove to be slow. This wasn't necessary before because rustc recently stopped using jemalloc by default. Fixes #1268
2019-04-24 23:21:38 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
checksum = "2022715d62ab30faffd124d40b76f4134a550a87792276512b18d63272333394"
alloc: use jemalloc when building with musl It turns out that musl's allocator is slow enough to cause a fairly noticeable performance regression when ripgrep is built as a static binary with musl. We fix this by using jemalloc when building with musl. We continue to use the default system allocator in all other scenarios. Namely, glibc's allocator doesn't noticeably regress performance compared to jemalloc. But we could add more targets to this logic if other system allocators (macOS, Windows) prove to be slow. This wasn't necessary before because rustc recently stopped using jemalloc by default. Fixes #1268
2019-04-24 23:21:38 +02:00
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
[[package]]
name = "glob"
deps: update glob dev-dependency
2019-04-14 22:57:08 +02:00
version = "0.3.0"
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "9b919933a397b79c37e33b77bb2aa3dc8eb6e165ad809e58ff75bc7db2e34574"
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
Move glob implementation to new crate. It is isolated and complex enough that it deserves attention all on its own. It's also eminently reusable.
2016-10-01 01:42:41 +02:00
[[package]]
name = "globset"
globset-0.4.6
2020-10-22 03:10:43 +02:00
version = "0.4.6"
Move glob implementation to new crate. It is isolated and complex enough that it deserves attention all on its own. It's also eminently reusable.
2016-10-01 01:42:41 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"aho-corasick",
"bstr",
"fnv",
"glob",
"lazy_static",
"log",
"regex",
"serde",
"serde_json",
Move glob implementation to new crate. It is isolated and complex enough that it deserves attention all on its own. It's also eminently reusable.
2016-10-01 01:42:41 +02:00
]
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
name = "grep"
grep-0.2.7
2020-05-29 15:17:24 +02:00
version = "0.2.7"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"grep-cli",
"grep-matcher",
"grep-pcre2",
"grep-printer",
"grep-regex",
"grep-searcher",
"termcolor",
"walkdir",
Move all gitignore matching to separate crate. This PR introduces a new sub-crate, `ignore`, which primarily provides a fast recursive directory iterator that respects ignore files like gitignore and other configurable filtering rules based on globs or even file types. This results in a substantial source of complexity moved out of ripgrep's core and into a reusable component that others can now (hopefully) benefit from. While much of the ignore code carried over from ripgrep's core, a substantial portion of it was rewritten with the following goals in mind: 1. Reuse matchers built from gitignore files across directory iteration. 2. Design the matcher data structure to be amenable for parallelizing directory iteration. (Indeed, writing the parallel iterator is the next step.) Fixes #9, #44, #45
2016-10-12 01:57:09 +02:00
]
grep-cli: introduce new grep-cli crate This commit moves a lot of "utility" code from ripgrep core into grep-cli. Any one of these things might not be worth creating a new crate, but combining everything together results in a fair number of a convenience routines that make up a decent sized crate. There is potentially more we could move into the crate, but much of what remains in ripgrep core is almost entirely dealing with the number of flags we support. In the course of doing moving things to the grep-cli crate, we clean up a lot of gunk and improve failure modes in a number of cases. In particular, we've fixed a bug where other processes could deadlock if they write too much to stderr. Fixes #990
2018-08-30 02:53:52 +02:00
[[package]]
name = "grep-cli"
grep-cli-0.1.5
2020-05-29 15:14:18 +02:00
version = "0.1.5"
grep-cli: introduce new grep-cli crate This commit moves a lot of "utility" code from ripgrep core into grep-cli. Any one of these things might not be worth creating a new crate, but combining everything together results in a fair number of a convenience routines that make up a decent sized crate. There is potentially more we could move into the crate, but much of what remains in ripgrep core is almost entirely dealing with the number of flags we support. In the course of doing moving things to the grep-cli crate, we clean up a lot of gunk and improve failure modes in a number of cases. In particular, we've fixed a bug where other processes could deadlock if they write too much to stderr. Fixes #990
2018-08-30 02:53:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"atty",
"bstr",
"globset",
"lazy_static",
"log",
"regex",
"same-file",
"termcolor",
"winapi-util",
grep-cli: introduce new grep-cli crate This commit moves a lot of "utility" code from ripgrep core into grep-cli. Any one of these things might not be worth creating a new crate, but combining everything together results in a fair number of a convenience routines that make up a decent sized crate. There is potentially more we could move into the crate, but much of what remains in ripgrep core is almost entirely dealing with the number of flags we support. In the course of doing moving things to the grep-cli crate, we clean up a lot of gunk and improve failure modes in a number of cases. In particular, we've fixed a bug where other processes could deadlock if they write too much to stderr. Fixes #990
2018-08-30 02:53:52 +02:00
]
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "grep-matcher"
ripgrep: release 12.0.0
2020-03-16 03:38:59 +02:00
version = "0.1.4"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"memchr",
"regex",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "grep-pcre2"
ripgrep: release 12.0.0
2020-03-16 03:38:59 +02:00
version = "0.1.4"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"grep-matcher",
"pcre2",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "grep-printer"
grep-printer-0.1.5
2020-05-09 16:33:02 +02:00
version = "0.1.5"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"base64",
"bstr",
"grep-matcher",
"grep-regex",
"grep-searcher",
"serde",
"serde_derive",
"serde_json",
"termcolor",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "grep-regex"
grep-regex-0.1.8
2020-05-09 16:31:29 +02:00
version = "0.1.8"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"aho-corasick",
"bstr",
"grep-matcher",
"log",
"regex",
"regex-syntax",
"thread_local",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "grep-searcher"
ripgrep: release 12.0.0
2020-03-16 03:38:59 +02:00
version = "0.1.7"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"bstr",
"bytecount",
"encoding_rs",
"encoding_rs_io",
"grep-matcher",
"grep-regex",
"log",
deps: replace memmap with memmap2 memmap is unmaintained at this point and it is being flagged as a RUSTSEC advisory in ripgrep. This doesn't seem like that big of a deal to me honestly, but memmap2 looks like a fine choice at this point. Fixes #1785, Closes #1786
2021-01-18 01:49:51 +02:00
"memmap2",
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"regex",
deps: run cargo update The only new dependency is an unused target specific dependency hermit via the atty crate.
2020-01-10 03:38:00 +02:00
]
[[package]]
name = "hermit-abi"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "0.1.18"
deps: run cargo update The only new dependency is an unused target specific dependency hermit via the atty crate.
2020-01-10 03:38:00 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "322f4de77956e22ed0e5032c359a0f1273f1f7f0d79bfa3b8ffbc730d7fbcc5c"
deps: run cargo update The only new dependency is an unused target specific dependency hermit via the atty crate.
2020-01-10 03:38:00 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"libc",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
Move all gitignore matching to separate crate. This PR introduces a new sub-crate, `ignore`, which primarily provides a fast recursive directory iterator that respects ignore files like gitignore and other configurable filtering rules based on globs or even file types. This results in a substantial source of complexity moved out of ripgrep's core and into a reusable component that others can now (hopefully) benefit from. While much of the ignore code carried over from ripgrep's core, a substantial portion of it was rewritten with the following goals in mind: 1. Reuse matchers built from gitignore files across directory iteration. 2. Design the matcher data structure to be amenable for parallelizing directory iteration. (Indeed, writing the parallel iterator is the next step.) Fixes #9, #44, #45
2016-10-12 01:57:09 +02:00
[[package]]
name = "ignore"
ignore-0.4.17
2020-11-23 17:25:33 +02:00
version = "0.4.17"
Move all gitignore matching to separate crate. This PR introduces a new sub-crate, `ignore`, which primarily provides a fast recursive directory iterator that respects ignore files like gitignore and other configurable filtering rules based on globs or even file types. This results in a substantial source of complexity moved out of ripgrep's core and into a reusable component that others can now (hopefully) benefit from. While much of the ignore code carried over from ripgrep's core, a substantial portion of it was rewritten with the following goals in mind: 1. Reuse matchers built from gitignore files across directory iteration. 2. Design the matcher data structure to be amenable for parallelizing directory iteration. (Indeed, writing the parallel iterator is the next step.) Fixes #9, #44, #45
2016-10-12 01:57:09 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"crossbeam-channel",
"crossbeam-utils",
"globset",
"lazy_static",
"log",
"memchr",
"regex",
"same-file",
"thread_local",
"walkdir",
"winapi-util",
commit Cargo.lock
2016-09-12 01:06:05 +02:00
]
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "itoa"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "0.4.7"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "dd25036021b0de88a0aff6b850051563c6516d0bf53f8638938edbb9de732736"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
alloc: use jemalloc when building with musl It turns out that musl's allocator is slow enough to cause a fairly noticeable performance regression when ripgrep is built as a static binary with musl. We fix this by using jemalloc when building with musl. We continue to use the default system allocator in all other scenarios. Namely, glibc's allocator doesn't noticeably regress performance compared to jemalloc. But we could add more targets to this logic if other system allocators (macOS, Windows) prove to be slow. This wasn't necessary before because rustc recently stopped using jemalloc by default. Fixes #1268
2019-04-24 23:21:38 +02:00
[[package]]
name = "jemalloc-sys"
deps: update everything
2019-06-17 00:38:45 +02:00
version = "0.3.2"
alloc: use jemalloc when building with musl It turns out that musl's allocator is slow enough to cause a fairly noticeable performance regression when ripgrep is built as a static binary with musl. We fix this by using jemalloc when building with musl. We continue to use the default system allocator in all other scenarios. Namely, glibc's allocator doesn't noticeably regress performance compared to jemalloc. But we could add more targets to this logic if other system allocators (macOS, Windows) prove to be slow. This wasn't necessary before because rustc recently stopped using jemalloc by default. Fixes #1268
2019-04-24 23:21:38 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "0d3b9f3f5c9b31aa0f5ed3260385ac205db665baa41d49bb8338008ae94ede45"
alloc: use jemalloc when building with musl It turns out that musl's allocator is slow enough to cause a fairly noticeable performance regression when ripgrep is built as a static binary with musl. We fix this by using jemalloc when building with musl. We continue to use the default system allocator in all other scenarios. Namely, glibc's allocator doesn't noticeably regress performance compared to jemalloc. But we could add more targets to this logic if other system allocators (macOS, Windows) prove to be slow. This wasn't necessary before because rustc recently stopped using jemalloc by default. Fixes #1268
2019-04-24 23:21:38 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"cc",
"fs_extra",
"libc",
alloc: use jemalloc when building with musl It turns out that musl's allocator is slow enough to cause a fairly noticeable performance regression when ripgrep is built as a static binary with musl. We fix this by using jemalloc when building with musl. We continue to use the default system allocator in all other scenarios. Namely, glibc's allocator doesn't noticeably regress performance compared to jemalloc. But we could add more targets to this logic if other system allocators (macOS, Windows) prove to be slow. This wasn't necessary before because rustc recently stopped using jemalloc by default. Fixes #1268
2019-04-24 23:21:38 +02:00
]
[[package]]
name = "jemallocator"
deps: update everything
2019-06-17 00:38:45 +02:00
version = "0.3.2"
alloc: use jemalloc when building with musl It turns out that musl's allocator is slow enough to cause a fairly noticeable performance regression when ripgrep is built as a static binary with musl. We fix this by using jemalloc when building with musl. We continue to use the default system allocator in all other scenarios. Namely, glibc's allocator doesn't noticeably regress performance compared to jemalloc. But we could add more targets to this logic if other system allocators (macOS, Windows) prove to be slow. This wasn't necessary before because rustc recently stopped using jemalloc by default. Fixes #1268
2019-04-24 23:21:38 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "43ae63fcfc45e99ab3d1b29a46782ad679e98436c3169d15a167a1108a724b69"
alloc: use jemalloc when building with musl It turns out that musl's allocator is slow enough to cause a fairly noticeable performance regression when ripgrep is built as a static binary with musl. We fix this by using jemalloc when building with musl. We continue to use the default system allocator in all other scenarios. Namely, glibc's allocator doesn't noticeably regress performance compared to jemalloc. But we could add more targets to this logic if other system allocators (macOS, Windows) prove to be slow. This wasn't necessary before because rustc recently stopped using jemalloc by default. Fixes #1268
2019-04-24 23:21:38 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"jemalloc-sys",
"libc",
]
[[package]]
name = "jobserver"
version = "0.1.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c71313ebb9439f74b00d9d2dcec36440beaf57a6aa0623068441dd7cd81a7f2"
dependencies = [
"libc",
alloc: use jemalloc when building with musl It turns out that musl's allocator is slow enough to cause a fairly noticeable performance regression when ripgrep is built as a static binary with musl. We fix this by using jemalloc when building with musl. We continue to use the default system allocator in all other scenarios. Namely, glibc's allocator doesn't noticeably regress performance compared to jemalloc. But we could add more targets to this logic if other system allocators (macOS, Windows) prove to be slow. This wasn't necessary before because rustc recently stopped using jemalloc by default. Fixes #1268
2019-04-24 23:21:38 +02:00
]
deps: update all deps
2017-12-30 22:48:25 +02:00
[[package]]
name = "lazy_static"
deps: update everything
2019-08-29 02:18:47 +02:00
version = "1.4.0"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
name = "libc"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "0.2.82"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "89203f3fba0a3795506acaad8ebce3c80c0af93f994d5a1d7a0b1eeb23271929"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
name = "libm"
version = "0.1.4"
deps: upgrade to memchr 2
2017-10-22 00:45:39 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
checksum = "7fc7aa29613bd6a620df431842069224d8bc9011086b1db4c0e0cd47fa03ec9a"
deps: upgrade to memchr 2
2017-10-22 00:45:39 +02:00
deps: update everything This adds one new dependency, maybe-uninit, which is brought in by crossbeam-channel[1]. This is to apparently fix some unsound code without bumping the MSRV. Since ripgrep uses the latest stable release of Rust, the maybe-uninit crate should compile down to nothing and just re-export std's `MaybeUninit` type. [1] - https://github.com/crossbeam-rs/crossbeam/pull/458
2020-03-15 14:32:33 +02:00
[[package]]
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
name = "log"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "0.4.13"
deps: update everything This adds one new dependency, maybe-uninit, which is brought in by crossbeam-channel[1]. This is to apparently fix some unsound code without bumping the MSRV. Since ripgrep uses the latest stable release of Rust, the maybe-uninit crate should compile down to nothing and just re-export std's `MaybeUninit` type. [1] - https://github.com/crossbeam-rs/crossbeam/pull/458
2020-03-15 14:32:33 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "fcf3805d4480bb5b86070dcfeb9e2cb2ebc148adb753c5cca5f884d1d65a42b2"
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
dependencies = [
"cfg-if 0.1.10",
]
deps: update everything This adds one new dependency, maybe-uninit, which is brought in by crossbeam-channel[1]. This is to apparently fix some unsound code without bumping the MSRV. Since ripgrep uses the latest stable release of Rust, the maybe-uninit crate should compile down to nothing and just re-export std's `MaybeUninit` type. [1] - https://github.com/crossbeam-rs/crossbeam/pull/458
2020-03-15 14:32:33 +02:00
deps: upgrade to memchr 2
2017-10-22 00:45:39 +02:00
[[package]]
name = "memchr"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
version = "2.3.4"
bump various versions
2016-12-30 22:43:29 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
checksum = "0ee1c47aaa256ecabcaea351eae4a9b01ef39ed810004e298d2511ed284b1525"
bump various versions
2016-12-30 22:43:29 +02:00
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
deps: replace memmap with memmap2 memmap is unmaintained at this point and it is being flagged as a RUSTSEC advisory in ripgrep. This doesn't seem like that big of a deal to me honestly, but memmap2 looks like a fine choice at this point. Fixes #1785, Closes #1786
2021-01-18 01:49:51 +02:00
name = "memmap2"
version = "0.2.0"
bump bytecount to 0.2 Signed-off-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>
2017-11-13 20:55:41 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: replace memmap with memmap2 memmap is unmaintained at this point and it is being flagged as a RUSTSEC advisory in ripgrep. This doesn't seem like that big of a deal to me honestly, but memmap2 looks like a fine choice at this point. Fixes #1785, Closes #1786
2021-01-18 01:49:51 +02:00
checksum = "e73be3b7d04a0123e933fea1d50d126cc7196bbc0362c0ce426694f777194eee"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"libc",
commit Cargo.lock
2016-09-12 01:06:05 +02:00
]
[[package]]
name = "num_cpus"
deps: small dependency updates
2020-04-18 17:33:27 +02:00
version = "1.13.0"
deps: update everything
2017-10-22 01:42:34 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "05499f3756671c15885fee9034446956fff3f243d6077b91e5767df161f766b3"
deps: update everything
2017-10-22 01:42:34 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"hermit-abi",
"libc",
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
]
regex: s/CachedThreadLocal/ThreadLocal CachedThreadLocal has been deprecated. We bump thread_local's minimal version corresponding to that deprecation as well.
2021-01-25 17:36:53 +02:00
[[package]]
name = "once_cell"
version = "1.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "13bd41f508810a131401606d54ac32a467c97172d74ba7662562ebba5ad07fa0"
deps: bump encoding_rs to 0.8.16 This brings in an updated `encoding_rs` crate that uses `packed_simd`, which compiles on the latest nightly. Compilation times do appear to be impacted significantly though. Fixes #1175 (again)
2019-02-08 00:05:14 +02:00
[[package]]
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
name = "packed_simd_2"
version = "0.3.4"
deps: bump encoding_rs to 0.8.16 This brings in an updated `encoding_rs` crate that uses `packed_simd`, which compiles on the latest nightly. Compilation times do appear to be impacted significantly though. Fixes #1175 (again)
2019-02-08 00:05:14 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
checksum = "3278e0492f961fd4ae70909f56b2723a7e8d01a228427294e19cdfdebda89a17"
deps: bump encoding_rs to 0.8.16 This brings in an updated `encoding_rs` crate that uses `packed_simd`, which compiles on the latest nightly. Compilation times do appear to be impacted significantly though. Fixes #1175 (again)
2019-02-08 00:05:14 +02:00
dependencies = [
deps: targeted update of some dependencies This updates encoding_rs, crossbeam-utils and crossbeam-channel. This serves two purposes. The encoding_rs update fixes a compilation failure on the latest nightly. The crossbeam updates are good sense and to reduce duplicate dependencies such as cfg-if. (Although, we note that the log crate still pulls in cfg-if 0.1, so ripgrep has a duplicate dependency there for now. But it's very small.) Fixes #1721, Closes #1705
2020-11-02 16:04:39 +02:00
"cfg-if 0.1.10",
"libm",
deps: bump encoding_rs to 0.8.16 This brings in an updated `encoding_rs` crate that uses `packed_simd`, which compiles on the latest nightly. Compilation times do appear to be impacted significantly though. Fixes #1175 (again)
2019-02-08 00:05:14 +02:00
]
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "pcre2"
deps: update to thread_local 1.0 We also update the pcre2 and regex dependencies, which removes any other lingering uses of thread_local 0.3.
2020-01-10 03:58:28 +02:00
version = "0.2.3"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "85b30f2f69903b439dd9dc9e824119b82a55bf113b29af8d70948a03c1b11ab1"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"libc",
"log",
"pcre2-sys",
"thread_local",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "pcre2-sys"
deps: upgrade pcre2-sys to 0.2.5 This brings in a PR that disables the JIT on certain Apple targets since it doesn't appear to build. See: https://github.com/BurntSushi/rust-pcre2/pull/16
2020-08-27 15:37:53 +02:00
version = "0.2.5"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: upgrade pcre2-sys to 0.2.5 This brings in a PR that disables the JIT on certain Apple targets since it doesn't appear to build. See: https://github.com/BurntSushi/rust-pcre2/pull/16
2020-08-27 15:37:53 +02:00
checksum = "dec30e5e9ec37eb8fbf1dea5989bc957fd3df56fbee5061aa7b7a99dbb37b722"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"cc",
"libc",
"pkg-config",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "pkg-config"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
version = "0.3.19"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
checksum = "3831453b3449ceb48b6d9c7ad7c96d5ea673e9b470a1dc578c2ce6521230884c"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "proc-macro2"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
version = "1.0.24"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
checksum = "1e0704ee1a7e00d7bb417d0770ea303c1bccbabf0ef1667dae92b5967f5f8a71"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"unicode-xid",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "quote"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "1.0.8"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "991431c3519a3f36861882da93630ce66b52918dcf1b8e2fd66b397fc96f28df"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"proc-macro2",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
name = "regex"
deps: bump regex and regex-syntax
2021-03-12 04:20:25 +02:00
version = "1.4.4"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump regex and regex-syntax
2021-03-12 04:20:25 +02:00
checksum = "54fd1046a3107eb58f42de31d656fee6853e5d276c455fd943742dce89fc3dd3"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"aho-corasick",
"memchr",
"regex-syntax",
commit Cargo.lock
2016-09-12 01:06:05 +02:00
]
deps: add bstr to Cargo.lock
2019-04-06 04:28:43 +02:00
[[package]]
name = "regex-automata"
deps: update everything This adds one new dependency, maybe-uninit, which is brought in by crossbeam-channel[1]. This is to apparently fix some unsound code without bumping the MSRV. Since ripgrep uses the latest stable release of Rust, the maybe-uninit crate should compile down to nothing and just re-export std's `MaybeUninit` type. [1] - https://github.com/crossbeam-rs/crossbeam/pull/458
2020-03-15 14:32:33 +02:00
version = "0.1.9"
deps: add bstr to Cargo.lock
2019-04-06 04:28:43 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "ae1ded71d66a4a97f5e961fd0cb25a5f366a42a41570d16a763a69c092c26ae4"
deps: add bstr to Cargo.lock
2019-04-06 04:28:43 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"byteorder",
deps: add bstr to Cargo.lock
2019-04-06 04:28:43 +02:00
]
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
name = "regex-syntax"
deps: bump regex and regex-syntax
2021-03-12 04:20:25 +02:00
version = "0.6.23"
deps: update regex crate This update brings with it a new feature of the regex crate which will now use SIMD optimizations automatically at runtime with no necessary compile time flags. All that's needed is to enable the `unstable` feature. Other crates, such as bytecount and encoding_rs, are still using the old-style SIMD support, so we leave the simd-accel and avx-accel features. However, the binaries we distribute on Github no longer have those features enabled, which makes them truly portable. Fixes #135
2018-03-10 21:02:06 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump regex and regex-syntax
2021-03-12 04:20:25 +02:00
checksum = "24d5f089152e60f62d28b835fbff2cd2e8dc0baf1ac13343bef92ab7eed84548"
deps: update regex crate This update brings with it a new feature of the regex crate which will now use SIMD optimizations automatically at runtime with no necessary compile time flags. All that's needed is to enable the `unstable` feature. Other crates, such as bytecount and encoding_rs, are still using the old-style SIMD support, so we leave the simd-accel and avx-accel features. However, the binaries we distribute on Github no longer have those features enabled, which makes them truly portable. Fixes #135
2018-03-10 21:02:06 +02:00
Update to memmap 0.6 `memmap` 0.6.0 introduces major API changes in anticipation of a 1.0 release. See https://github.com/danburkert/memmap-rs/releases/tag/0.6.0 for more information. CC danburkert/memmap-rs#33.
2017-10-29 00:32:43 +02:00
[[package]]
name = "ripgrep"
12.1.1
2020-05-29 15:26:47 +02:00
version = "12.1.1"
Update to memmap 0.6 `memmap` 0.6.0 introduces major API changes in anticipation of a 1.0 release. See https://github.com/danburkert/memmap-rs/releases/tag/0.6.0 for more information. CC danburkert/memmap-rs#33.
2017-10-29 00:32:43 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"bstr",
"clap",
"grep",
"ignore",
"jemallocator",
"lazy_static",
"log",
"num_cpus",
"regex",
"serde",
"serde_derive",
"serde_json",
"termcolor",
"walkdir",
Update to memmap 0.6 `memmap` 0.6.0 introduces major API changes in anticipation of a 1.0 release. See https://github.com/danburkert/memmap-rs/releases/tag/0.6.0 for more information. CC danburkert/memmap-rs#33.
2017-10-29 00:32:43 +02:00
]
deps: update other dependencies to latest
2018-08-20 13:39:43 +02:00
[[package]]
name = "ryu"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
version = "1.0.5"
deps: update other dependencies to latest
2018-08-20 13:39:43 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
checksum = "71d301d4193d031abdd79ff7e3dd721168a9572ef3fe51a1517aba235bd8f86e"
deps: update other dependencies to latest
2018-08-20 13:39:43 +02:00
Don't search stdout redirected file. When running ripgrep like this: rg foo > output we must be careful not to search `output` since ripgrep is actively writing to it. Searching it can cause massive blowups where the file grows without bound. While this is conceptually easy to fix (check the inode of the redirection and the inode of the file you're about to search), there are a few problems with it. First, inodes are a Unix thing, so we need a Windows specific solution to this as well. To resolve this concern, I created a new crate, `same-file`, which provides a cross platform abstraction. Second, stat'ing every file is costly. This is not avoidable on Windows, but on Unix, we can get the inode number directly from directory traversal. However, this information wasn't exposed, but now it is (through both the ignore and walkdir crates). Fixes #286
2017-01-08 17:27:30 +02:00
[[package]]
name = "same-file"
deps: update everything
2020-01-17 02:47:23 +02:00
version = "1.0.6"
Don't search stdout redirected file. When running ripgrep like this: rg foo > output we must be careful not to search `output` since ripgrep is actively writing to it. Searching it can cause massive blowups where the file grows without bound. While this is conceptually easy to fix (check the inode of the redirection and the inode of the file you're about to search), there are a few problems with it. First, inodes are a Unix thing, so we need a Windows specific solution to this as well. To resolve this concern, I created a new crate, `same-file`, which provides a cross platform abstraction. Second, stat'ing every file is costly. This is not avoidable on Windows, but on Unix, we can get the inode number directly from directory traversal. However, this information wasn't exposed, but now it is (through both the ignore and walkdir crates). Fixes #286
2017-01-08 17:27:30 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "93fc1dc3aaa9bfed95e02e6eadabb4baf7e3078b0bd1b4d7b6b0b68378900502"
Don't search stdout redirected file. When running ripgrep like this: rg foo > output we must be careful not to search `output` since ripgrep is actively writing to it. Searching it can cause massive blowups where the file grows without bound. While this is conceptually easy to fix (check the inode of the redirection and the inode of the file you're about to search), there are a few problems with it. First, inodes are a Unix thing, so we need a Windows specific solution to this as well. To resolve this concern, I created a new crate, `same-file`, which provides a cross platform abstraction. Second, stat'ing every file is costly. This is not avoidable on Windows, but on Unix, we can get the inode number directly from directory traversal. However, this information wasn't exposed, but now it is (through both the ignore and walkdir crates). Fixes #286
2017-01-08 17:27:30 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"winapi-util",
Don't search stdout redirected file. When running ripgrep like this: rg foo > output we must be careful not to search `output` since ripgrep is actively writing to it. Searching it can cause massive blowups where the file grows without bound. While this is conceptually easy to fix (check the inode of the redirection and the inode of the file you're about to search), there are a few problems with it. First, inodes are a Unix thing, so we need a Windows specific solution to this as well. To resolve this concern, I created a new crate, `same-file`, which provides a cross platform abstraction. Second, stat'ing every file is costly. This is not avoidable on Windows, but on Unix, we can get the inode number directly from directory traversal. However, this information wasn't exposed, but now it is (through both the ignore and walkdir crates). Fixes #286
2017-01-08 17:27:30 +02:00
]
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "serde"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "1.0.119"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "9bdd36f49e35b61d49efd8aa7fc068fd295961fd2286d0b2ee9a4c7a14e99cc3"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "serde_derive"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "1.0.119"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "552954ce79a059ddd5fd68c271592374bd15cab2274970380c000118aeffe1cd"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"proc-macro2",
"quote",
"syn",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
[[package]]
name = "serde_json"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "1.0.61"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "4fceb2595057b6891a4ee808f70054bd2d12f0e97f1cbb78689b59f676df325a"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"itoa",
"ryu",
"serde",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
Pass the simd-accel feature to encoding_rs
2017-08-20 08:35:02 +02:00
[[package]]
deps: update to latest regex crate The regex update fixes the Rust nightly build failure by in turn updating its simd dependency to 2.x. The regex update also includes a literal optimization that uses Tuned Boyer Moore. Fixes #617
2017-12-30 22:46:55 +02:00
name = "strsim"
deps: update to clap 2.33
2019-04-06 15:37:33 +02:00
version = "0.8.0"
Pass the simd-accel feature to encoding_rs
2017-08-20 08:35:02 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "8ea5119cdb4c55b55d432abb513a0429384878c15dde60cc77b1c99de1a95a6a"
Pass the simd-accel feature to encoding_rs
2017-08-20 08:35:02 +02:00
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
[[package]]
name = "syn"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "1.0.58"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "cc60a3d73ea6594cd712d830cc1f0390fd71542d8c8cd24e70cc54cdfd5e05d5"
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"proc-macro2",
"quote",
"unicode-xid",
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
]
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
[[package]]
Completely re-work colored output and tty handling. This commit completely guts all of the color handling code and replaces most of it with two new crates: wincolor and termcolor. wincolor provides a simple API to coloring using the Windows console and termcolor provides a platform independent coloring API tuned for multithreaded command line programs. This required a lot more flexibility than what the `term` crate provided, so it was dropped. We instead switch to writing ANSI escape sequences directly and ignore the TERMINFO database. In addition to fixing several bugs, this commit also permits end users to customize colors to a certain extent. For example, this command will set the match color to magenta and the line number background to yellow: rg --colors 'match:fg:magenta' --colors 'line:bg:yellow' foo For tty handling, we've adopted a hack from `git` to do tty detection in MSYS/mintty terminals. As a result, ripgrep should get both color detection and piping correct on Windows regardless of which terminal you use. Finally, switch to line buffering. Performance doesn't seem to be impacted and it's an otherwise more user friendly option. Fixes #37, Fixes #51, Fixes #94, Fixes #117, Fixes #182, Fixes #231
2016-11-20 18:14:52 +02:00
name = "termcolor"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
version = "1.1.2"
deps: update termcolor to 1.0.0
2018-07-18 00:37:02 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update everything Most of these updates come from releases I've made, and the rest appear minor. No new dependencies have been added, and `const_fn` was removed. Yay.
2021-01-18 01:55:03 +02:00
checksum = "2dfed899f0eb03f32ee8c6a0aabdb8a7949659e3466561fc0adf54e26d88c5f4"
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"winapi-util",
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
]
bump clap to 2.26 Fixes #482
2017-07-31 00:04:49 +02:00
[[package]]
name = "textwrap"
deps: update to clap 2.33
2019-04-06 15:37:33 +02:00
version = "0.11.0"
bump clap to 2.26 Fixes #482
2017-07-31 00:04:49 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
bump clap to 2.26 Fixes #482
2017-07-31 00:04:49 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"unicode-width",
bump clap to 2.26 Fixes #482
2017-07-31 00:04:49 +02:00
]
update deps
2016-10-30 04:27:29 +02:00
[[package]]
name = "thread_local"
regex: s/CachedThreadLocal/ThreadLocal CachedThreadLocal has been deprecated. We bump thread_local's minimal version corresponding to that deprecation as well.
2021-01-25 17:36:53 +02:00
version = "1.1.2"
update deps
2016-10-30 04:27:29 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
regex: s/CachedThreadLocal/ThreadLocal CachedThreadLocal has been deprecated. We bump thread_local's minimal version corresponding to that deprecation as well.
2021-01-25 17:36:53 +02:00
checksum = "d8208a331e1cb318dd5bd76951d2b8fc48ca38a69f5f4e4af1b6a9f8c6236915"
update deps
2016-10-30 04:27:29 +02:00
dependencies = [
regex: s/CachedThreadLocal/ThreadLocal CachedThreadLocal has been deprecated. We bump thread_local's minimal version corresponding to that deprecation as well.
2021-01-25 17:36:53 +02:00
"once_cell",
update deps
2016-10-30 04:27:29 +02:00
]
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
[[package]]
name = "unicode-width"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
version = "0.1.8"
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
checksum = "9337591893a19b88d8d87f2cec1e73fad5cdfd10e5a6f349f498ad6ea2ffb1e3"
Switch from Docopt to Clap. There were two important reasons for the switch: 1. Performance. Docopt does poorly when the argv becomes large, which is a reasonable common use case for search tools. (e.g., use with xargs) 2. Better failure modes. Clap knows a lot more about how a particular argv might be invalid, and can therefore provide much clearer error messages. While both were important, (1) made it urgent. Note that since Clap requires at least Rust 1.11, this will in turn increase the minimum Rust version supported by ripgrep from Rust 1.9 to Rust 1.11. It is therefore a breaking change, so the soonest release of ripgrep with Clap will have to be 0.3. There is also at least one subtle breaking change in real usage. Previous to this commit, this used to work: rg -e -foo Where this would cause ripgrep to search for the string `-foo`. Clap currently has problems supporting this use case (see: https://github.com/kbknapp/clap-rs/issues/742), but it can be worked around by using this instead: rg -e [-]foo or even rg [-]foo and this still works: rg -- -foo This commit also adds Bash, Fish and PowerShell completion files to the release, fixes a bug that prevented ripgrep from working on file paths containing invalid UTF-8 and shows short descriptions in the output of `-h` but longer descriptions in the output of `--help`. Fixes #136, Fixes #189, Fixes #210, Fixes #230
2016-11-13 04:48:11 +02:00
update deps
2016-10-30 04:27:29 +02:00
[[package]]
libripgrep: initial commit introducing libripgrep libripgrep is not any one library, but rather, a collection of libraries that roughly separate the following key distinct phases in a grep implementation: 1. Pattern matching (e.g., by a regex engine). 2. Searching a file using a pattern matcher. 3. Printing results. Ultimately, both (1) and (3) are defined by de-coupled interfaces, of which there may be multiple implementations. Namely, (1) is satisfied by the `Matcher` trait in the `grep-matcher` crate and (3) is satisfied by the `Sink` trait in the `grep2` crate. The searcher (2) ties everything together and finds results using a matcher and reports those results using a `Sink` implementation. Closes #162
2018-04-29 15:29:52 +02:00
name = "unicode-xid"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
version = "0.2.1"
update deps
2016-10-30 04:27:29 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
checksum = "f7fe0bb3479651439c9112f72b6c505038574c9fbb575ed1bf3b797fa39dd564"
update deps
2016-10-30 04:27:29 +02:00
commit Cargo.lock
2016-09-12 01:06:05 +02:00
[[package]]
name = "walkdir"
deps: update everything
2020-01-17 02:47:23 +02:00
version = "2.3.1"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "777182bc735b6424e1a57516d35ed72cb8019d85c8c9bf536dccb3445c1a2f7d"
commit Cargo.lock
2016-09-12 01:06:05 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"same-file",
"winapi",
"winapi-util",
commit Cargo.lock
2016-09-12 01:06:05 +02:00
]
deps: update all deps
2017-12-30 22:48:25 +02:00
[[package]]
name = "winapi"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
version = "0.3.9"
deps: update all deps
2017-12-30 22:48:25 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bring in all semver updates This brings in all other semver updates. This did require updating some tests, since bstr changed its debug output for NUL bytes to be a bit more idiomatic.
2020-11-02 17:06:13 +02:00
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
deps: update all deps
2017-12-30 22:48:25 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
deps: update all deps
2017-12-30 22:48:25 +02:00
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
version = "0.4.0"
deps: update all deps
2017-12-30 22:48:25 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
deps: update all deps
2017-12-30 22:48:25 +02:00
deps: update various deps This includes a new crate, winapi-util, that is now used in wincolor, walkdir and same-file.
2018-08-25 06:19:40 +02:00
[[package]]
name = "winapi-util"
deps: update all dependencies Everything looks pretty minor.
2020-05-09 15:05:51 +02:00
version = "0.1.5"
deps: update various deps This includes a new crate, winapi-util, that is now used in wincolor, walkdir and same-file.
2018-08-25 06:19:40 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
deps: update various deps This includes a new crate, winapi-util, that is now used in wincolor, walkdir and same-file.
2018-08-25 06:19:40 +02:00
dependencies = [
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
"winapi",
deps: update various deps This includes a new crate, winapi-util, that is now used in wincolor, walkdir and same-file.
2018-08-25 06:19:40 +02:00
]
deps: update all deps
2017-12-30 22:48:25 +02:00
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
deps: update several dependencies We specifically avoid updating tempdir since it seems to have grown a dependency on `remove_dir_all`, which in turn still uses winapi 0.2.
2018-02-11 20:31:41 +02:00
version = "0.4.0"
deps: update all deps
2017-12-30 22:48:25 +02:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump pcre2-sys This should bring a compilation time improvement when building static buils of PCRE2 by enabling parallelism for C compilation. Kudos to @JoshTriplett for the tip!
2020-08-20 00:55:16 +02:00
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
Reference in New Issue Copy Permalink